Mikael Sandberg Community Champion

You have to use {{sprint.xxx}}, the sprint is not tied to the issue itself, the issue only holds a reference to it. You can see the different options for the Sprint smart value here.

Jira Cloud doesn’t have a version.

The reason it asking you here on the Community to select the product is so that your question ends up in the right product category.

Hi @Reynalda Torres, Welcome to Atlassian Community! Jira has three different types of projects, Jira Service Management (JSM), Jira Software (JSW), and Jira Work Management (JWM) to simplifying it a bit. You can see what type of project you are using by looking up in the left-hand corner, it will say either Service…

You need to have project admin permissions in order to configure automations, and once you have that permission you will find automation under Project settings.

Hi @Patrick, Welcome to Atlassian Community! JSM has an integration for this called Atlassian Assist which is based on Halp and does exactly the things you are looking for, and it is included in your standard plan and up.

Hi @Chris Johnson, Welcome to Atlassian Community! The Alerts that you see in the menu on the left-hand side in a JSM project is coming from Opsgenie, and are generated by services you defined in there and what you are monitoring. Based on what you are describing you are for something different. You should look at…

Hi @Lydia Roth, Welcome to Atlassian Community! Since you are using a dot as part of the field name I would recommend that you use the custom field identifier instead, like {{issue.customfield_12345.format("dd/MM/yyyy")}}. You can get the custom field ID if you to go Settings > Issues > Custom fields. From here locate the…

Hi @Mohammed Abdul, Welcome to Atlassian Community! You can set the start and completion date automatically either as a post function or via an automation. For example when the engineer moves transition the change to Implementing the start date is automatically set, and when change is moved to completed the Completed date…

The gadget is based on the resolution field, not the status. So in order for the Created vs Resolved gadget to work correctly you have to make sure that the resolution is set when moving an issue to closed. You can either do that by having a screen associated with the transition to closed, or set the resolution as part of…

The short answer is no, the user picker field cannot return the email address. The reason is GDPR. What you can do is once you have the accountId you get the email via the Users resource.

No, the resolution date cannot be changed, it is set at the time the resolution is set.

That is just a warning that external integrations may not function after the renaming. There are no consequences within Jira, since it redirect any links to the old project key to the new one. 

Correct, currently you cannot configure the board on a JWM project. There is a suggestion to add that feature, JWMCLOUD-25.

You are correct, if you are using the default gadgets that comes with Jira you have to first create the filter and make sure it is shared with the users that needs to see the result, I would recommend that you share it with the project, and then you can use it in a gadget. Your other option is to use an app like Custom…

No, a sub-task cannot have a sub-task.

All existing links in Confluence to Jira will still work since Jira keeps track of the old project key and will redirect any links to the old key to the new key. So your customers would still be able to get from your KBs to the linked issue without any issues.

The short answer is no, you cannot change that text, that is predefined by Atlassian and there is no settings that will change it.

You need to have at least project admin permissions, then go to the project, select Project settings > Details and from here you can change the project lead. 

Hi @Svetlana, Welcome to Atlassian Community! Yes, you can change the issue type, all you have to do is use the Move function and move it to an Epic. Just go to the task you want to change and click on the three-dot menu and select Move and then follow the instructions.

Short answer is no, once you deleted an issue there is no way of restoring it without a backup. The recommendation is to change your permission scheme to limit who should be able to delete issues in order to avoid situations like this.

Hi @[deleted], Welcome to Atlassian Community! You can contact Trello Support here without having to log on to your account. 

You can use smart value to get the summary, in this case it is {{issue.summary}}. You can then use that to edit the summary field, something like this {{issue.summary}} - {{now.format("dd/MM")}}

No, it is now part of JSM. It used to be that you needed a Halp subscription, but that was before Atlassian Assist.

Hi @Gabriel, Welcome to Atlassian Community! Since you are on JSM Premium you have access to Atlassian Assist, built on Halp, which does exactly what you are asking for. 

The short answer is no, you can not change the default workflow associated with a project template. At least not for now, there is a suggestion to add that feature, see JRACLOUD-7020 

Go to Customer notification > Approval required and see if you checked the box "Exclude person who caused the action". Also, if you are the reporter of the request you may get different results, I know SLAs are sometimes not triggering if you are both the reporter and the assignee on a request.

Hi @Chad Jackson, Welcome to Atlassian Community! If you select the Attach forms action you have the option to select which form to attach, and if it should be internal or external.

Hi @Adi, Welcome to Atlassian Community! It is the far-most right column on the board that determine if an issue is done in the sprint or not. You mentioned that you changed the workflow, so make sure that your mapping between columns and statuses are set correctly. You do that from Board settings > Columns. 

Are the users in the group getting other emails from Jira? When I tested it with the approver group it took a bit longer to receive the email, but it did show up as expected.