Mikael Sandberg Community Champion

The user that you tested this with, are they assigned a JSM license?

You can do this by setting the opsbar-sequence property on your transitions. Go to the workflow and add it. It is recommended that you use set the value to 10, 20, 30 etc, that way if you ever have to update your workflow and add it as the 5th option you can do that by setting the opsbar-sequence to 42 without having to…

You could give a group agent access to only use the reply to customer by giving them comment permission. What controls if you can reply to the customer is the JSM license.

In order to reply to customer the user has to be an agent and be assigned a JSM license. If a customer is added as a request participants they can add replies via the Portal.

Your other option is to use the Get fields paginated endpoint and use the custom field id to get the name and other information.

Hi @Hakob Abajian, Welcome to Atlassian Community! What you see is expected, any custom fields that you are using in the request form will show up as customfield_xxxxx in the API. You can figure out the names of these if you go to Jira settings > Issues > Custom fields. Then locate the fields that you have on the request…

No, customers are free and do not require a license, it is only agents that require a license.

You have to do it using smart value and the advanced branch in order to do it, like this:

It sounds like you have a post function in the workflow that sets the resolution. You can change that if you edit your workflow and remove that post function.

@john cook I cleaned up the text to remove PII information since this is open to everyone.

If you are looking for your cloudid information you can get that by making a call to https://api.atlassian.com/oauth/token/accessible-resources, see Get the cloudid for your site for more information.

Another option that you may have tried would be to use the same automation as mentioned above and add a second one that is an incoming webhook that does the actual lookup of the QA tasks, that way you could create them at the beginning.

There is a request to have that possibility to set permissions for who can change the layout, JSWCLOUD-21540 that you can vote on and watch.

In the new UI you have two things that control the issue layout, the screen(s) and the issue layout. Changing the issue layout in a project that is sharing the screen will not affect the other projects, but you could copy the layout to keep them the same across the board. And no, you cannot prevent a project admin from…

So here is what I would do. I would only create the QA task(s) once all the other tasks are done, that will take some of the complexity out of the automation. So you could use the rule in the library called When all stories are completed → then close epic as your starting point, but instead of doing the transition you…

Hi @Jennifer, The field you are looking for is called request-channel-type, and you can use that in your JQL like this: request-channel-type = portal 

So you could use a service account and set that as the owner of the automation and then forward emails sent to that account to your JSD queue.

Hi @James Lango, Welcome to Atlassian Community! You will not be able to hide the menu, but you could restrict access to the object schema. If you go into the object schema and then click on the object schema button up in the right hand corner and select Configure > Roles. From here you define which users and groups that…

You cannot create a Kanban board in a JSM project, that is specific for Jira Software projects. But what you can do in a company-managed JSW project is to modify the filter that the Kanban board is using so it also include the JSM project, that is how I do it for all of our change requests so we can plan our work in…

That is correct!

Anytime you use the labels field in a filter you also have to account for the case where the labels field does not have a value. So in your case your filter should look something like this: (labels != XX OR labels is EMPTY)

Sorry, my bad. It should be under Space settings > Restricted.

You can use bulk edit to remove yourself as a watcher. Just go to Filters > Advanced issue search and use this filter: watcher = currentUser() Then click on the three-dot menu up in the right hand corner and select bulk change. Note that the filter only returns the first 1000 issues so you would have to repeat this until…

You do not have to go to the page to do it, go to the space that the page is in, and from here you can remove the restrictions as I outlined above.

Hi @raza.perez, Welcome to Atlassian Community! As a space admin you can go in and remove page restrictions, just go to Space settings > Manage pages > Hidden, and from here you can delete page restrictions, just click on the pad lock. This will take you to Page information and you can delete the restrictions under Page…

You two options to do this, you can either add the component field to the request form and make it hidden and give it the components you want on that request. Your other option would be to use automation and add the components when the request is created.

If you go to Project settings > Automation and look under Library you will find a rule just for that called When all stories are completed → then close epic.

No, currently the section only support a single question as a condition.

You can use the endOfWeek() and startOfWeek functions to do this. This one should do it: custom_date_field > startOfWeek("+1") AND custom_date_field < endOfWeek("+1")

You can use issue security to do this on the issue level, and you can find out more information about it here. In out-of-the-box Jira you cannot set field permissions, you would need an app in order to do that.