Mikael Sandberg Community Champion

Did these issues exist before you applied the issue security scheme? Existing issues are not affected if you apply a new security scheme and setting a level as default, that only applies to new issues. For the existing ones you can do a bulk update and set the security level.

Hi @john.monteith, Welcome to Atlassian Community! Since your automation that updates field D based on field C and field C is changed via an automation you have to make sure that you check Allow rule trigger on the one that updates field D:

In order to set the assignee you would first have to find the Atlassian Id for that user, which you can do by doing a web request to the Find user endpoint.

You can exclude current (open) sprints and future sprints by using these two functions in your JQL: sprint not in openSprints() AND sprint not in futureSprints()

Hi @Harry, Welcome to Atlassian Community! If the summary will always have the same format the you can use the split String separator function to get each of the 4 subsections, something like this: {{issue.summary.split("|").first}} -> Test Summary {{issue.summary.split("|").second}} -> FOO User

Hi @Vince Tkac, Welcome to Atlassian Community! The short answer is no, you cannot change the order. It will aways show the current user first and then the other assignees in alphabetical order. 

You can only copy an automation from one space to another from Global automation. From there you can change the scope of the copied automation to the new space.

The smart value is either the field name or the custom field Id: {{issue.fieldname}} {{issue.customfield_XXXXX}} Sub-tasks are treated the same way as a regular issue. You can get the custom field Id if you go to Settings > Issues > Custom fields, locate the field and then hover over one of the options under the three dot…

@Cosmo Denger it all depends on how your global permission for JSM is set up. Just adding Service Project Customer - Portal Access to the issue security does not automatically open up all requests to everyone in the company. If your global permission is set to not automatically share with the org nothing will change. And…

You have two options, either use {{issue.support team}} or use the custom field Id {{issue.customfield_XXXXX}}. You can find the Id if you go to Settings > Issues > Custom fields, locate the custom field in question and hover over one of the menu options under the three dot menu. The URL contains the Id at the end of it.

Hi hailey.clement@foodsconneted.com, Welcome to Atlassian Community! Those are either variables or placeholder text. Variables will prompt you enter text into them when you create a new page, and placeholder text can be used to add instructions. Check out this KB for more information. 

You can also chain automations this way, for example if you have one that triggers on issue create it can then trigger the next one by sending a web request to it and so on.

This can be done if you set up your new rules to be triggered via web request, and then make the call to it from the main automation. I have several automations that is set up this way, my main automation is basically a dispatch that sends web requests to trigger other automations.

Hi @Warren Zingel, Welcome to Atlassian Community! If you go to Project settings > Issues do you see the issue type there? If not, click Actions > Edit issue types and see if it is listed under Available issue types. If it is, then just drag it over to the Issue Types for Current Schema and save it. If the issue type is…

Hi @Alexis Antonio Arriaga Herrera, Welcome to Atlassian Community! Yes, that is possible. Queues are just filters, so you could create a queue that filters out requests that belong to a specific team/assignee if you like. 

Hi @kim.fox, Welcome to Atlassian Community! You cannot hide the SLA section if the issue has an active SLA. The only time that section is hidden is if there are no SLAs for that issue. The only workaround would be to use an app instead of the built-in SLA, I know that Time to SLA allows you to hide it, but my guess is…

Could it be a reference to that you can update to ProForma Full without loosing existing forms? That's my understanding after reading the documentation for it, Upgrading from ProForma Lite to ProForma Full. 

Hi @Aguirre, Alan (ESI), Welcome to Atlassian Community! One of the Atlassian Support Engineers that are on here will reach out to you in order to resolve this for you. 

Hi @tara wilding, Welcome to Atlassian Community! Have a look at this template rule from the Automation Playground that closes issue that have been inactive for a certain amount of time. The query in its simplicity would look something like this: updated < -2d

That is the attribute view, you need to go to the object view, and from there select the list view, see this KB for more information.

What type of project is it, company managed or team managed? If it is a company managed project the assignee filter is based who have access to your instance, it is not just limited to who have access to the project.

Hi @Oleksandr Holiiad, Welcome to Atlassian Community! After you added the new status, go to the object list view, from here you can do a bulk edit of the listed objects.

It is showing up because you are using the basic view, it cannot use the organizationMembers() function, and that is why you see the error. You have to use the JQL view in order to use that function.

That is the security level field, so the field name you are looking for is Security Level.

Hi @Akash Sharma, Welcome to Atlassian Community! Is organizationMembers an user, or are you trying to see issues that members of a specific organization? If the latter then you have to use JQL and the organizationMembers() function, something like this: reporter in organizationMembers("Atlassian")

the short answer is no, not unless you have an app that supports it (I can't remember if Better Excel exporter did it or not), you create your own app that uses the API or you have access to Analytics. The issue key is a combination of the display name and the URL that is combined in the GUI.

Because of the way the assignee via round-robin works I don't think there is much more clean up you can do. Unfortunately there isn't a way to get the user who would be next in the round-robin so you could compare if that user is the same as the developer.

Hi @Matteo Gabanini, Welcome to Atlassian Community! If you by restriction field means the one that sets the security on the issue then you are looking for the field called security level.

Hi Theresa, Welcome to Atlassian Community! If you go to one of the issues that you moved to done, is the resolution also set? You should see it next to the status with a checkmark. If the resolution is not set then Jira is consider the issue to still be unresolved and that is why it is not deducted from the progress bar.…

@Elizabeth Jones This might be a bit late, but I missed your post, and just discovered that I also get the same error. It looks like now you have to use the custom field Id instead of the name, so the JSON should look something like this: { "fields": { "customfield_xxxxx": { "id": "<Category Id>" } } }