Mikael Sandberg Community Champion

It can be done, you would have to use the Get component REST endpoint to get the component lead. {{issue.components}} will give you the ID of the component. Note that your automation needs to check if there are more than one component since the field can have multiple values.

Hi @shyun, Welcome to Atlassian Community! Yes, you can add multiple approval statuses if needed, I have multiple workflows that have two or more approval statuses. 

Jira OnDemand was the old name for Jira Cloud...

Yes, it can be done by using the Message Custom Field type, there is one for edit screen and one for the view/default screen that you can use for this.

Yes, that is possible. Your SLAs are based on JQL, so you could base it on organizations. Have a look at Create SLA goals based on customer details for more information.

The main difference has to do with your issue type scheme. If you add a new issue type to your project it will use the workflow that is set to unassigned types, instead of a workflow that is assigned to a specific type. 

Hi @Rozalina Tsvetkova Welcome to Atlassian Community! You need an app to get that result, out-of-the-box JQL cannot do nested queries that is needed to get the feature and issues under it. I have used JQL Tricks and Enhanced search in the past to do that, but check the Marketplace because the are other apps that can do…

It should work on any issue type, including sub-tasks. If you do the assignment within the rule that creates the sub-task then you would need to use the related issue branch and select the most recent created issue. Note that if you have multiple sub-tasks that you create that should be assigned to the same user, I would…

It sounds like you have a workflow condition that requires all child issues to be in a done status before you can close out your epic. For the issue that is in the Not Required status, is that status a done status? You can tell by the color, if it is green then it is a done status. Also, is the resolution set on that…

Hmm, I'm wondering if it could be that you left out the whitespace before and after the = sign. Anyway, if you use the same AQL in Assets and replace the customfield part, do you get a result then? Btw, here is the article that introduced filter…

You can find the differences if you go What are team-managed and company-managed projects? and also check out this article, Company-Managed vs Team-Managed Projects in Jira .

Hi @Fen_Stormon, Welcome to Atlassian community! The assign issue component in Automation can assign based on a project role, so you could use that. That would cover the case when the user is replaced, then all you would have to do is adding the new user to the correct role.

You need a JSM license in order to edit Assets, so you would have to assign the user a license for the Assets menu to be shown. Jira Software and Jira Work Management users can only view and edit the content of an Assets custom field.

Hi @William Rentfrow, Welcome to Atlassian Community! Try and remove the () around the custom field in the filter scope. Here is an example of how my peripheral field is set up that is filtered based on the selected location.

Hi @farshideh kordi, Welcome to Atlassian Community! Your question is better suited for Xilinx Community Forums, my bet is that you ended up on the Atlassian Community because you clicked help and then Ask the community in Confluence. 

Yes, that can be changed if you go to Settings > Products > Advanced Roadmaps dependencies. From here you can set the default link type and also add more if needed.

Hmm, I don't know if the automation in Assets can do it, but I do know that Automation can do it. You can find automation under Project settings in your project (assuming that you are on the latest version of JSM). 

The only way to get the count would be to use an automation to get the size returned from an object lookup. You could make the rule a scheduled one and if the returned size is < 10 send a notification.

The smart value would be {{issue.Worked Today}} or {{issue.customfield_xxxxx}}. You can get the custom field number if you click on the three dot menu and over over one of the options, the URL displayed will show the ID at the end.

Basic JQL can only pull a known parent and the issues that are children of it, something like this: parentEpic in (JRA-123, JRA-456)

You need an app that extends JQL in order to do this. JQL out-of-the-box cannot do a nested query that gets you this result. Check the Marketplace for apps that can do this for you.

Something like this should do it for you: "Status" IN ("On stock") AND "Model" IN ("13-inch Mac")

Hi @Greta Mezzina, Welcome to Atlassian Community! No, you do not have to have a verified domain in order to remove someone as org admin. If you are on the original admin console (see the KB you linked to) just go to Settings > Administrators. From here you can add and remove org admins. 

Customers do not have to have an Atlassian account in order to access JSM, they can be just portal-only customers. Correct, if the customer is not either a portal-only customer there is no way of changing the reporter, it would just be a generic account in that case, and as an agent you would not be able to contact the…

Have you mapped your workflow statuses to the columns on the board? Is it only new issues that are not showing up, or are none of the showing? The first thing I would check is the status mapping to columns.

On the reopened request, is the resolution still set? That would explain why it is showing up under the closed request filter. Check your workflow to make sure that the resolution is cleared when it is reopened.

Hi @Esti Cohn, Welcome to Atlassian Community! If the multi choice question is a Jira field then yes, you would have to create a new field for it. If you are using Forms then you will get a text box that the user can fill out, or you could use a condition that will show a free text field of Other is selected.

Hi @Adam Callaghan, Welcome to Atlassian Community! You need an app in order to get the result you are looking for. There are multiple apps in the Marketplace that extends JQL like JQL Tricks and Enhanced Search, both of which I have used before.

If you do use a custom field and the agent set it when they contact the customer you could configure the automation in a way that do not need an extra status. All it would have to do is transition the request to a status that stops the SLA, and then transitioning it back to the original status.

What data do you get if you use {{webhookData.employees}} in a log action? Basically just go down the levels in the JSON file that is coming into the webhook to figure out what gives you the data.