Mikael Sandberg Community Champion

Try using a incognito window or a different browser. That is what I have to do because I have multiple accounts.

Is the assignee set when the issue is created? That would explain why it is not showing up in the history, since the initial create doesn't show what fields were filled out.

The user picker field is populated from the list of active users that have access to your Jira instance, so you would not have to maintain multiple lists if you have multiple user picker fields. 

Just to add to @Ste Wright answer, the execution option for automations is only available in the new issue view, your screenshots indicate that you are using the old issue view (which by the way is going away pretty soon).

You would have to add the Slack member ID as a property on the user, here is a good article about how to do it, Mention someone directly in Slack via Jira Automation.

No, you can do both a message to a Slack channel and DM's, just note that you have to use the Slack member ID for the user you want to DM.

I haven't, the only endpoints I used for the status is submitProgress and getStatus for the mapping.

Hi @Jennifer Thobois, Welcome to Atlassian Community! Yes, that is possible by using automation and have it trigger on the transition to your closed status. You would need to have an app in Slack for incoming webhooks, but that is pretty easy to create, here is an tutorial for it.

Unfortunately automations doesn't have an API that you can use to export/import your rules. Regarding copying production data, I know that Atlassian is working on backup and restore APIs and according to the public roadmap the EAP is scheduled for Q3-Q4 2023.

Is the request type field set on the issue that you are using for testing? {{issue.url}} will get you the internal URL, the customer facing one is only available if request type is set.

Hi @Patricia Limbu, Welcome to Atlassian Community! The editor does not support html code, it only support markdown notation, but you can include the link by using the smart value {{issue.url.customer}}.

You have to do it from the UI or via the API endpoint for attributes, the mapping cannot create new attributes.

Verify attribute values to be unique it the documentation for it, but basically you go to the Attribute list and click on the cog wheel on the right and under general you can set the attribute to be unique.

It should be based on the attribute that is set as unique. The label is just used to display the objects in the list on the left-hand side.

The issues are accessible if you have a direct link to them, and after 60 days the project and the issues will be permanently deleted.

Issue security works in conjunction with the permission scheme. The issue security defines who have access to the issue based on your role, group, single user, etc. My recommendation is to use roles instead of groups, because that allows you to control the access from within the project instead of having to add and remove…

Hi @sam smith, Welcome to Atlassian Community! No, removing a queue will not remove the issues in it. A queue is just a view based on a filter. 

Hi @Will Savage, Welcome to Atlassian Community! Does your objects in Assets have an user type attribute? Did you check the import report to see if you got any errors while doing the import? 

You have to create a new scheduled automation (but you do not have to save it), the JQL is part of the schedule. Just click the checkbox for "Run a JQL search..." and you will see the where you can enter your JQL. Then just click validate query and you will get the total number of issues found.

So something like this should do it for you assuming that it is the last comment: {{issue.comments.last.body.substringBetween("Work Order No: ", "Origination")}}

Just to add on to this, the Assign to on-call responder only supports a single user, so if you have more than one person on-call you need to work around that. The solution I have for it is using Tray.io ,(but you could use another automation platform if you want) to pick a responder on random and then set them as the…

Turns out that this is a known bug, AUTO-261, and it is being worked on. The workaround is to change the rule actor to a user that have access to both JSM and Opsgenie. 

Hi @David Fawkes, Welcome to Atlassian Community! You can do that with smart values and automation. The smart values for text fields have lots of options to extract substrings from a field. For example I am using this in one of our automations to find Prisma Alert Ids: {{issue.description.substringBetween("This was Prisma…

Yes, there is, you can use the Add issue types to issue type scheme endpoint.

Hi @Red Hendery, Welcome to Atlassian Community! You would have to manually add the new issue type to each scheme, there is no bulk function to do that. Just go to Settings > Issues > Issue type schemes and start adding it. 

Currently it is scheduled for Q1-Q2 2023 according to Atlassian's public roadmap.

At the moment that is not possible. A workaround, once the API for forms is released, would be to take the information in the form and add it to either the description field or a custom field that is added to the description fields section of the layout.

Hi Matt, Welcome to Atlassian Community! Yes, it is possible to search on tasks that the user is assigned to or is supporting, the easiest would be if the supporting custom field is a user picker field. Your JQL would then look something like this: assignee = <Atlassian ID> OR supporting = <Atlassian ID> You do not have to…

Hi @Corey Dawson, Welcome to Atlassian Community! The short answer is no, you cannot change the order so that the form is shown above subtasks. 

You are using the wrong API, the one you are using is for external assets and not the one in JSM. The API you are looking for can be found here, Assets. That API is using the workspace ID to know which instance to go to, so your URL would look something like this: https://api.atlassian.com/jsm/assets/workspace/...