Mikael Sandberg Community Champion

Hi @Olga D, Welcome to Atlassian Community! Automation for Jira is a service account and is needed by Automation so it can trigger automation rules in your project. This is similar to other apps that need specific access in projects in order to work. 

You can find the documentation here, https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/

Okay, now I see what you are saying. Yes, inline images are not available for the description field, anything you add will be added as an attachment. It is only comments that support it. There is a suggestion to change the description field on the portal to be the same markdown editor as within Jira, JSDCLOUD-9072. 

I believe the new workflow editor is still rolling out. If you click on Add post function, at the bottom you should see Update Issue Field and from here you should be able to set the resolution. The other option is to associate the transition with a screen that has the resolution field on it.

Are you editing the workflow in the new or the old workflow editor? You know if you are in the new one if you see these options at the top:

@Sheri Widler Currently the answer is no, teams in advanced roadmaps is not available outside of advanced roadmaps. You should be able to do it once the new Atlassian Teams has been rolled out, you can learn more about it here.

AQL does not have the same functions for dates as JQL, but if you use this it should work: "Last Access Audit" < now(-180d)

Hi @Mario Amaya (x), Welcome to Atlassian Community! Is the assignee set via another automation? Or how is the assignee set? My guess is that your automation that sends the Slack message is running before the assignee is set and that is why you are not seeing it. 

Hi @Mark Chiasson, Welcome to Atlassian Community! There is currently an active issue with Microsoft email that is impacting the email handler in JSM, so if you are using Microsoft that would explain it. Please check https://jira-service-management.status.atlassian.com/ for the latest status. 

Because you are setting it up as a scheduled rule you also have to check the box for "Run a JQL..." just as in the example I linked to: And you can add your conditions to the JQL instead of having separate components for it.

It all depends on if you are using Form (formerly ProForma Forms) or the request form as I mentioned above. Here is an example of using the request form: As you can see the Description field is accepting rich text. Here is an example of Form: As you can see the "Describe in more detail" is not accepting rich text, and that…

Hi @Vincent Ivory, Welcome to Atlassian Community! Check out this rule in the automation library, you can use that as a template for the one you are looking to create. Basically you create a scheduled one that looks at updated date and in the verification status and if so, then notify the verifier that the issue needs to…

Perfect, I will do that!

Okay, so it looks like your issue is not linked to an epic and that is why the rule is not passing the second condition. So when you create your issue you also have to link it to your epic for the automation to work.

You would need an app in order to do this, like Scriptrunner or Power Scripts. I know from experience that Scriptrunner has a function that would allow you to make fields required based on values in another field.

What does you rule look like? Based on the audit log it is failing on related issues condition.

My guess it that the regex for the file name needs to match the whole name, so try using this one and see if it works: Data Privacy.*

Hi @Jasmine Pennala, Welcome to Atlassian Community! The way you have the automation set up currently would mean that the issue that is triggering it would get the value from itself. Here is an automation that we have that copies the fix version from the epic:

You would need an app in order to do it, like Refined for Jira which allows you to create different portals.

Either by adding a comment to the trigger issue, or you have the option to send an email, or sending them a slack message if you are syncing the Slack ID to the user's property as described in this article.

Hi @GrEgory Prins, Welcome to Atlassian Community! You have stumbled over the external assert platform API, not the one that is for the Assets that Atlassian provides if you are on JSM Premium. Here is the REST API document for Assets. 

Yes, as you mentioned you can just not create the sub-task if the field isn't empty and in that case notify the user the reason why the sub-task was not created.

Hi @Juliane Matern Welcome to Atlassian Community! No, Software projects still do not have a summary dashboard similar to Work Management projects, but there are ways around it like creating a dashboard and link it in the project.

There is currently an EAP for Board and backlog enhancements so maybe Atlassian will add the feature to switch status within the same column, a lot of new features are aligning team-managed projects and company-managed projects. You could join the EAP and suggest to have that feature added.

Hi @Sebastian Villalobos, Welcome to Atlassian Community! You could do this using Assets and scope filtering if you are on the premium plan. All you would need is a field that the user first select, like owner, and that would filter out the relevant processes for that owner in the second field. The article above has a good…

Hi @DW, Welcome to Atlassian Community! What you see is expected, you cannot change the status within a single column that is mapped to multiple statuses. The only way around it is to move that statuses to their own column so that you have a 1-to-1 mapping instead of 1-to-n. 

The Id for the pull request in the picture is 541, to id under it is the short commit Id.

Currently you can only access the data in the form in an automation rule if you have linked the form fields to Jira fields. Atlassian is releasing an API for Forms in the near future, currently the public roadmap has it scheduled for Q2 2023, which has an endpoint that allows you to get the data out of the form.

And if you are copying the category from the trigger issue the JSON would look like this: { "fields": { "Category": { "id": "{{triggerissue.Category.id}}" } } }

The category is a special custom field, and can only be set by using the More options and the advanced field editing. You need to find the ID for the category you want to set, one way of doing that is to have manual triggered automation that has a log action that you set to {{issue.Category}}. This is what the JSON would…