Mikael Sandberg Community Champion

What custom field type are you using for the email address? What endpoint are you using to get the data from Jira?

This is expected, the automation only have access to the data in the issue at the time it was triggered. You can add the Re-fetch issue data after the edit of approvers and that should solve the issue.

To show/hide fields in the form based on conditions you add sections which has the option to always show or based on a condition. The condition is linked to a previous field, and that field has to be one of the four choice fields that are available. You can learn more about it…

Have a look at Examples of using smart values with dates for more examples on how you can manipulate dates.

Hi @Dan Foster, Welcome to Atlassian Community! You could check which day of the week the request was created like this {{issue.created.dayOfWeekName}} and then check the diff between created date and start date to figure out the priority. 

You need to use the Atlassian ID for the assignee field, so you would have to use the web request component to send a request to either Get account IDs for users or find users and then get the ID from the result. Your JSON should look something like this: { "fields": { "assignee": { "id": "{{webhookData.accountId}}" } } }

Okay, try this: {"update": {"approvers": [{"remove": {"name":"{{initiator}}"}}]}}

Oh, wait, I just noticed that you are on server. So try this in the advanced edit: { "update": { "approvers": [ { "remove": "{{initiator}}" } ] } }

Is the approvers field a user picker field or a text field? Based on your log it makes me thing that you are using a text field, because if you are using a user picker field {{issue.approvers}} should give you the Atlassian Id instead of the email address.

Hi @Jean-Philippe Ehret, Welcome to Atlassian Community! The documentation you found is most likely for Confluence Data Center, the change history macro for Confluence Cloud does not have any parameters that you can set. 

Updating issues via import is only available for Jira admins, other users can only import new issues if that global permission has been enabled. The update import has to be initiated by going to Settings > System > External System Import.

Just a side note to @George Kopsachilis answer. The Create object is not only available under Global automation, you can use that from within project automation as well.

When you are adding/removing a user from a user picker field you have to use the Atlassian Id, and that is why you get the Token is empty error. The advanced edit should look something like this:

A reference is a connection between objects. If the current object has an attribute that reference another object, that reference becomes an outbound reference. If another object is pointing toward the current object then the reference is an incoming reference. Example: You gave to objects, Person and Asset. The asset has…

Hi @graham.pinnock, Welcome to Atlassian Community! You can use the Jira macro to do this, it will add a list of Jira issues based on a filter that you define. And you can also configure which fields should be visible in the table.

Okay, so I would check your People settings and who have been added to the Service Desk Team role and compare that between the two projects. It could be that in the project you are not assigned a role that there is a group that you belong to have been added to the Service Desk Team role.

In the other project that you are not admin in, what role do you have in that project?

Just to add to @Kai Becker answer, make sure that you are also in the Service Desk Team role on both projects, that would give you the right permissions if you are using the default permission scheme.

The documentation you found only applies for Jira Server/Data Center. For Jira Cloud you can download the Rich Text Gadget for Jira which is a free app.

Short answer is no, Forge is only for Cloud. Data Center is using a different code base and has a separate SDK for app development.

You need to edit your workflow and use the reuse transition to replace Resolved with Done. By using the reuse you do not have to configure each transition. Note that in order to update the workflow you need to be Jira admin.

Yes, it is possible to use a single automation that spans multiple projects. In your case I would use the if/else condition to check which project it is and then set the component accordingly. You can change the rule from being a single project rule to multi-project if you go to Settings > System > Global automation and…

Btw, looks like the deadline to sign up has passed, but you could always try, there might still be availability.

The EAP for issue level archiving is scheduled to go live March 27 and run for about 6 months. You can find out more about the EAP and how to sign up for it here, Issue level archival in Jira Cloud: EAP signup 

Hi @Andrew Groom, Welcome to Atlassian Community! The short answer is no, you cannot have a subset of users be on Premium while the rest are on Standard. All users within Jira has to be on the same level. You may want to take a look at the Marketplace, there are multiple apps in there that have similar features to Advanced…

If you uncheck the "Only include issues..." that should help. Because you are checking the due date it should should only include issues one time in the automation. Here is what I would do, make a copy of your rule and instead of sending an email just create a log action that you set to maybe {{issue.key}} and then run the…

Any fields that are set to required in the field configuration will give you an error if they are not visible on the screen. So you would have to modify your field configuration to make the fields optional in the field configuration for it to work.

Hi @Aimane SBAI, Welcome to Atlassian Community! Short answer on both use cases are no, you cannot hide specific objects for some users, nor can you hide specific objects based on status. What you can do in the second use case is to filter out objects with a specific status, but that only applies to each user. 

The easiest way to troubleshoot is to run the JQL and see how many issues it returns. 

Yes, that’s correct. You have to ask your Jira admin to create a custom field called Regression.