Mikael Sandberg Community Champion

You can if you base the card color on queries. You could then use a custom field, like say card color, and set that field via automation when the due date is exceeded.

Hi @vijay, Welcome to Atlassian Community! The majority of the project templates can be either company managed or team managed, with exception for JSM and product discovery. You choose which type the project will be on the screen where you enter the name and project key, just click More options:

In order to create a custom field that gets its values from versions, just like fix versions and affected versions, you have to use one of the two version picker field types which you can find under Advanced when creating the custom field.

So the automation should be pretty straight forward, something like this should do it, just change the triggering transition and the destination transition:

No, both allows creation of new accounts, for the first one it depends on both your global customer access settings and project setting, here is the KB explaining it. It comes down to if you want to control customer access on the project level or on a global level.

Hmm, okay check if Settings > Products > Email requests that either of the top two options for Account creation for customer is selected

If you didn't already have a branch, then it would look something like this:

Hi @Jeff Kirkpatrick, Welcome to Atlassian Community! Because you are already using the branch component your only option to add the watcher to the new issue would be to use a web request to a second rule that sets the watcher and you can include reporter as part of the request body. 

Have you also enabled "Customers can access and send requests from the portal without logging in"?

Check your Customer permissions on the project and make sure you have selected "Anyone allowed on the customer access settings" under Service project access.

Hi @Aesha Chauhan Welcome to Atlassian Community! The Get issue endpoint will get you all the fields that you are looking for.

Something like this should do the trick:

The easiest solution that I can think of would be to create a scheduled automation that sets the specific customer as request participant on those tickets. All you need is a JQL that picks up all those issues and then once the automation is created you manually run it. 

Did you integrate your JSM project with Assist? Once that integration is done, any requests created from Slack will be available in the portal and the user will get notified if there is an update done to the request from the JSM side. Yes, Assist/Halp has its own ticketing system, but you can ignore that unless you want to…

The easiest is to look up in the left hand corner, if the project is either JSW or JSM it will say that under the project name. If it is a JWM project you will see that based on the menu, its at the top instead of on the left side. You can also go to Projects > View all projects and look at the type to see what kind of…

Hi Abe, It is only possible if you have an app that extends JQL, out-of-the-box JQL does not support nested queries. I know from experience that you can do this with Enhanced Search/Scriptrunner and JQL Tricks, but there are other apps in the Marketplace that can do this too.

@Carmela Marco this should be it's own question, but the impact would be that any existing emails would have dead links to them if you move a way from JSM, and you would have to reconfigure Opsgenie to work with the new tool.

No, Assets is only available if you are on the JSM Premium plan or Enterprise plan. You can see what features are available for each plan if you go to https://www.atlassian.com/software/jira/service-management/pricing

You are getting the error because there is not "Re-Open Ticket" transition from the Resolved status, based on your workflow the only transition you have from Resolved is Close. You would need to add a "Re-Open Ticket" transition from Resolved to Waiting for support for the automation to work.

@Ivan Rubio renaming the values in a select field will affect existing issues. If you do not want to do that then you can disable the existing value and add a new one, that way the user can then select to change it later if needed.

The reason done epics are showing up in the epic link field is because epics are a bit different from other issues in that besides the normal status it also has an epic status, and that is what controls if it should show up in that list or not. Have a look at this KB on how you can fix this by using a post function if you…

Correct, the diff ignores that time and will only return the diff in days. And no, you would not need to "print" the diff, you can use it as is in an advanced compare if condition like this: The rule will not go past this compare unless the compare is true.

Hi @Daniel Cotter, Welcome to Atlassian Community! Instead of creating different workflows you could do this using automation, that way it can scale when you need to add new request types. Then all you would have to do is in your workflow set the Jira field to Approvers group, and then have the automation set the…

Hi @Michael Smith, Welcome to Atlassian Community! You could manipulate the two dates to see if there is a difference based on number of days, like this: {{issue.due.diff(issue.resolved).days}}

@Nolan McConnell that article only applies to Jira Cloud not Jira Server/Data Center and only for the detailed view when viewing the issue from a board.

You need to get him to create a group, teams are not yet available in Automation. Team is just in it's early stages, more features around should be coming in Q3-Q4 2023 based on Atlassian's public roadmap.

Haha, for me it has just been grinding and experience ever since we started using JSM 2+ years ago. Automations are now a big part of it and we keep coming up with new use cases all the time.

It's been a while since I used Jira on Server/Data Center but i am pretty sure that those fields that you are seeing right now are the only ones that can be at the top.

Hi @Landen Crabill, Welcome to Atlassian Community! The EAP for the backup and restore APIs are currently scheduled for Q3-Q4 2023 based on Atlassian's public roadmap.

No, Jira Server/Data Center does not allow you to move fields up to the top section of the detailed issue view.