Mikael Sandberg Community Champion

Hi @Monica Vijaywargi, Welcome to Atlassian Community! It sounds like you have a screen on the transition to Done that includes the resolution field. If you add a step before the transition that edit the Resolution field the error message should go away.

You should be able to use {{issue.key}} in your lookup query, since you at that point is on the epic level, not the triggering issue.

Hi @Boyd K, Welcome to Atlassian Community! You can use the announcement banner to do this, take a look at Configuring an announcement banner for more information. 

Your automation would look something like this: In this case I am getting the approvers for the selected application, you can just change the edit issue fields to set the assignee instead.

Hi @Ben Scott, Welcome to Atlassian Community! The field type you are looking for is called Paragraph, that will give you a multi line field similar to Description. 

Hi @Narendra Haridasu, Welcome to Atlassian Community! You can do this by going to Filters > Advanced issue search and create a filter that shows the stories you wan tot change the date one, and then do a bulk edit to set the new date. 

It depends, if you are using a company-managed project the answer is yes. If you are using a team-managed project the answer is no.

No, there is no REST endpoint that will give you the roles used for each project, you would have to use Get project roles for project for each of your projects.

Hi @Iwona Czardybon, Welcome to Atlassian Community! Yes, that is correct, you have to change the global permissions in order to disable users from creating team-managed projects. Nothing else needs to be changed. 

No, the number of site/org admins doesn't affect your subscription cost, what affects the cost is the total number of users for each application.

Yes, you need to move the done ones to the far right in order to set the resolution. Yes, you could remove that column, just note that you would then have to map the statuses in that column to one of the other columns.

Okay, so in a team-managed project you cannot set the resolution, in those projects it is set when you move the issue to the far right column. So I would check the configuration of your board. Have the board changed lately? Was the done status moved to a different column? Was a new column created? Did the workflow change?…

If you look on your left-hand side when you are in the project, does it say "You're in a team-managed project" or company-managed project?

The KB mention that you can fix the resolution by changing your workflow, but you can also do that using an automation similar to this

If you go to the detailed view of the issue, if the resolution is set you should see this The status is on the left and the resolution is on the right. If you do not see the resolution it explains why the show up on the backlog. Please have a look at this KB for best practices on using the resolution field.

Hi @shawker Welcome to Atlassian Community! Is the resolution field set on those Done issues? If the resolution is not set Jira will consider the issue to be unresolved, no matter what status it is in, and therefor show up on the backlog. 

Then just skip that part and use the JQL branch, the smart value {{issue.Parent Link}} will give you the parent issue.

Okay, so you are using the Parent link field to link your epics to initiatives. So in that case you would have to create a smart value and use the JQL branch like this: This is a very simplified example, I would add a check that the transitioned issue is an epic.

In your project, go to Project settings > Permissions, and from here click Actions > Use a different scheme and then select the new scheme you created.

It would be similar to what I posted yesterday above. Instead of using the blocks link type that I used, you could specify your own link type to indicate the relationship between initiatives and epics. Then in the branch, check for that specific link type.

If you go to Licenses you will see all that are associated with your account.

Hi @richard_kim, Welcome to Atlassian Community! If you go to my.atlassian.com you can add more technical contacts and billing contacts for your subscriptions and licenses. 

You cannot use the parent branch to do this, since parent only applies to subtasks, and the parent epic only applies to stories/tasks linked to an epic. In this case you have to use the linked issues option.

You are correct, the JQL needs to be changed. It should look something like this: "Request Type" = Email(MWTR) status = "QA" and updated < -48h This should give you all Email request type in the QA status that have not been updated in the past 48 hours.

I missed that you are dealing with two different projects. In this case you have to configure the automation to be under the Global administration, then from the Rule details you can change the automation to be for multiple projects.

Hi @Trayce Larochelle, Welcome to Atlassian Community! The billing is not based only on the number of users you have, it is also based on the Plan you are on. By default when you sign up for a new instance it gives you 30 days of free usage of the standard plan. You can always the plan you are subscribed to by going to…

Hi @Justin Princehorn, Welcome to Atlassian Community! You could use the "When all stories are completed → then close epic" automation in the Library as your start Instead of the transition at the end, replace that one with the Send email action.

Hi @Lauren Briskin, Welcome to Atlassian Community! No, and epic cannot have multiple start/end dates. So the workaround in you case would be to break up the epic in two different ones. 

Hi @Jerard Alden M. Tabunda, Welcome to Atlassian community! Cloud applications don't have a version number since they are constantly being updated. 

So based on your requirements the automation would look something like this: This one checks the status on the blocked issue (in your case X-1) and that both Y-1 and Z-1 are in the status Done and if so, move X-1 to done as well.