Mikael Sandberg Community Champion

Hi @[deleted], Welcome to Atlassian Community! Do you happen to be using Chrome or Safari on a macOS 13.6/14.0 device? There is an issue with that combo that is causing UI glitches that results in web browser elements, links, tabs, etc. becoming unresponsive and not being clickable (we have internal users that is seeing…

Currently forms are not supported in Assist, there is a suggestion to have that added, see JSDCLOUD-13190. I would suggest that you go there and add your vote to it.

You want to check what the value is for {{issue.EIS Group}} when it has multiple values, I suspect that it is not in a format that AQL understands and that is why it if not returning anything. AQL is expecting it to look something like this: KEY in ("key-1", "key-2")

Yes, that is possible and you can find the instructions here. Jira comes with a default mail handler, so you do not have use an external one.

Hi @Ben, The documentation you found only applies to Data Center, the documentation for Cloud and access to products can be found here. If you disable a user then you are not being billed for that user. Having site access count as an active user, but if you are not using Atlassian Access then that user would not count…

Hi @madhuri kaniganti, Welcome to Atlassian Community! It would be possible, you would have to modify the workflow that you are using in JPD and then have an automation that transitions the idea to the right status based on the reporter. 

You have to use the display name or the member ID that the user have in Slack for the @ mention to work. If all your users are using the default firstname.lastname as the display name then this should work for you: {{#issue.approvers}}@{{displayName.replace(" ", ".").toLowerCase}}{{^last}}, {{/}}{{/}} If some of your users…

No, it returns the characters, from the specified amount of characters, from the right of the text string. Example, if summary is Hello World! then {{issue.summary.right(6)}} -> World!

So if we use your example above then the smart value would look like this: {{issue.summary.right(17)}} This should give you User is having trouble logging into the application.

Do not open the raw email by clicking on the file, instead open it in a text editor and you will see the raw email.

Hi Ana, This should be fairly simple to do with automation and smart values. If the custom field is of the date type then all you need to do in your automation is to assign the value of that custom field to the start date/due date like this: You can learn more about smart values here.

Here is the article that announced the name change.

Hi @David Terrano, Welcome to Atlassian Community! Roadmap is now called Timeline and if you go into the project you should see it on the left. The basic timeline is available for all plans, including the free.

You can do this by using smart values, the ones for text fields can remove part of the string. If the prefix in your summary has a set number you could use right(int length) to get the text you want. If it is not a set number then one of the substring functions should work.

To take a screenshot on Windows 10/11 press Windows logo key + Shift + S, on MacOS press command + Shift + 4. You can then use the Insert photos button to add it here.

The update should be immediately after the automation has run. What does your automation looks like?

On Cloud these are the default ones: It has been 3+ years since I used Jira Server/DC but I found this article that shows the default ones on Server/DC. 

Correct, once you delete a space it is permanently deleted and the only way to restore it is from backup. 

What will happen if you remove resolution is that issues that are in a done status will still be considered open by Jira. For example the created vs resolved report would show that you have not resolved any issues since that report relies on the resolution field. Another thing that you will notice is that if you set the…

Here is an article the describe what you can do in Cloud. Basically you get the user's Slack Id and add it to their Atlassian account as a property, and then in an Automation you access that property to @ mention the user in Slack. 

No, that trigger will only run at the time when a SLA breach, it will not trigger on SLAs that have already breached. For the ones that have already breached you can use a scheduled automation and use a JQL that picks up those breached ones. The JQL would look something like this: "Time to First Response" = breached()

Hi @J. Lewis, Welcome to Atlassian Community! Without knowing the Slack Id of the user you want to @ mention it is not possible. If you where on Jira Cloud you could add the Slack Id as a user property and then use that in your automation, but Jira DC do not currently have anything similar. There is a suggestion to have…

Hi Alice, Welcome to Atlassian Community! JSM is different from other flavors of Jira in that it is using both issue types and request types. A single issue type can be linked to multiple request types. So I would use the request type to track the different requests you get.

You would need an app that extends JQL in order to do this since JQL out-of-the-box do not have a date compare. There are multiple apps in the Marketplace that extends JQL, and it looks like JQL search extensions for Jira has a date compare function.

It can be done without an app, but you would need to use the API in order to get the data since it is not recorded in the history log. You can use the Get sla information endpoint to get the data. You can then use this in an automation to populate the custom field that you have, just note that if you have a lot of old…

Hi @Zaldy Parian, Welcome to Atlassian Community! SLAs cannot auto close an issue when the SLA is breached, in order to do that you have to use automation. The SLA is just a way of tracking how well you are meeting the level of service expected. Automation has a trigger called SLA threshold breach that you can use to auto…

In Jira the workflow is in the center of everything, and your starting point will be the initial status for the issue. In the screenshot I included above the initial status is To Do. The board columns have statuses mapped to them, but that mapping is 1:1, so you cannot map the To Do status to more than one column. Unlike…

That is not the raw email, it should look something like this: Return-Path: <email address> Received: from <mail server> (<mail server> [ip address]) by inbound-smtp.us-west-2.amazonaws.com with SMTP id <id> for <email address>; Wed, 18 Oct 2023 18:09:00 +0000 (UTC) X-SES-Spam-Verdict: PASS X-SES-Virus-Verdict: PASS ...

I haven't moved an issue over from a team managed project to a company managed one if you have custom field in it. But you can export all issues to a csv file and then import them into the new project and make sure that fields are mapping correctly.

Yes, you can do this in Jira Work Management, but you have to use issue security and a company managed project. Using different roles would not prevent someone with access to the project to see all issues. Issue security is the only way to do this.