Jack Brickey Expert

If you wish to use custom fields for this you will need to leverage and automation/scripting addon (automation for jira, Scriptrunner, power scripts, etc). If you can leverage Compoments then you could Assignee a default assignee by component.

You will need to leverage Automation to achieve these behaviors. I use Automation for Jira but there are certainly others and you may already have one, e.g. Scriptrunner, Power Scripts, etc

Because in Jira there isn’t an inherit parent-child relationship between Story and Task. They are at the same level from a hierarchy perspective. Epic Story1 Story2 Subtask1 Subtask2 Subtask3 Task1 Subtask1 Subtask2

Ok I misread what you were asking. I thought you were saying you renamed a status and wanted to rename it back. What you are saying is that you cannot transition the issue back to the previous status. That means (most likely) there is no transition in place for you to do so. If you are the admin then edit the workflow and…

You only need the second part if you run the query well into the next week or beyond, I.e. you are querying outside of the current week.

Try this... * Copy the filter ID from logs * go to your filters and click on one of them * click in the URL field of browser and replace the filter number at the end of the URL

Sort of yes. To be precise the other project likely does not have the status that is mapped to the Waiting column, which may or may not be “waiting”. For example the mapped status might be “hold” or similar. Regardless of this detail you are likely correct, I say likely because there are other, less likely causes, e.g. the…

You can certainly simply bookmark the portal url and access. If you want the full experience create a gmail test customer.

Is it possible that your admin has disabled creation of projects other than NG?

Isn’t it backwards? After -7d is recent. Also, are you only interested in issues where the status changed or could it be any update?

create a Jira group, add members and give the group Browse, comment, etc. permissions.

Agreed. Not sure I can help on identifying the source of CAB and if it even matters here. 

I’m not where I can test and give precise input but if you go to Jira settings > issues > custom fields and find your field the click on the ellipses you should be able to configure and set the default. 

We can't say what CAB is as it is a group defined by one of your admins. Look at the members of the group to see if you can discern it's purpose. Now for emailing all customers in an organization, unless something has changed, there is no way to do this using the Organization name. You could create a group and manually add…

not sure I understand.

Yes that is Automation for Jira. Try to set up a scheduled automation Under the when/trigger.

No. To treat you uniquely an admin will need to remove you from any common role/group and place you in a unique role/group. If you are the admin go to project settings - notifications and inspect what is in place. If you are not the admin reach out to them and they will know what to do.

I would not use Tasks but rather sub-tasks under stories. In this way things work more cleanly IMO. 

What automation are you using? In Automation for Jira you can set up an automation to trigger on a schedule, e.g. daily. When triggered it would find all issues that match a JQL and transition to Closed.

If “escalate” transition is exposed to the portal then yes they can. Check out your workflow. What it “means” depends on what your team defines it to mean.

You need to have the admin make changes to align with needs. It may be that batch emails would be a good idea. Of course you need to consider what others need as well.

You should have the admin engage here rather than being a middle-man. Note you can’t make jira application publicly accessible which includes dashboards. Users must be licensed.

Then you need to find a way to incorporate the date it entered the status associated with backlog and still in that status. This is not simple and I would refer you to an old post that does a good job explaining this. I recommend adding a custom date field (entered backlog) and use a post function to add the current date…

Unfortunately you cannot change this.

You will want to use Jira Service Desk. You might refer to the documentation to learn more.

Why can you not change it back? What are you experiencing exactly?

Try something like this. Use a label or similar qualification for reopened issues and exclude the label in your goals. Add the label (sla-exclusion) via a post function on reopen transition. The goal should look something like this: ....and labels != sla-exclusion... I have not tried this but should work. You will need to…

It depends on how issues enter your backlog. Typically this occurs when an issue is created. assuming that try the following Project = xxxxx and status = "To Do" and createdDate <= startOfDay(-2w)

The last column is what Jira uses to process “complete sprint”.

Yes, Order by priority will follow how you have them ordered in the configuration as mentioned previously.