Mikael Sandberg Community Champion

Hi @gdakas, Welcome to Atlassian Community! It is possible, and you can check which group the user belongs to in an if branch, similar to this automation that I have the sets the site based on where the user is located:

The short answer is no, and it is because the condition on the SLA doesn't allow you to exclude a user. I'm curious, why are you using an automation to add comments to the request when it is created and not using the customer notifications? 

Okay, so I am not following. You said that you created a new custom field the other day, but the information has always been there... The JQL doesn't care when the information/field was added, unless you are searching on specific dates or date ranges. So if all your issues have a value set for "Caller's Email[Short text]"…

You can get the service desk Id if you go to the portal and select your project, the Id will be part of the URL. The same thing applies to the request type Id, if you go to it in the portal you will see the Id as part of the URL. You can also get these Ids via the REST API, Get service desks and Get all request types

@Anita Szabo This should be it's own question, but it is always recommended that when you restore that you do that on the same major version number. There are database changes that have been made between 7.x.x and 9.x.x so there are no guarantees that the restore will work.

You want to change the JQL and remove the currentUser() and instead replace that with the Atlassian ID of the client. You can get the ID by going to Customers under Channels & People, locate the customer and go to their profile. The URL will have the ID.

Assuming that you want to do this in a request form, take a look at this guide on how to link two insight custom fields using scope filtering.

So what you need to do is configure the permission schemes that all your projects are using so that Browse Projects permissions is not given to everyone. I would recommend that you use a project role, that way project admins can control who have access to the project. You can learn more about how permissions work here.

So the JQL that you are using will only give you issues that where created within the last 30 days, if you remove created >= 30d you would get all the issues that you are looking for.

Yes, it is possible and since you are on Jira Cloud you also have access to Automation. Just go to Project settings > Automation and create the rule from here. Your rule would look something like this:

What you see is by design, Rank is a system field that is only used internally by Jira to set the order on the board and it has no meaning to a user.

Your filter that you are using on your dashboard will only return data based on it. So if you are searching on a field that you just created yesterday, that is what you will get back, unless you go back on older issues and add the information.

Yes, changing SLAs has always only applied to active issues in that SLA. 

Currently this is not possible unless you link your fields to a Jira field. There is an API coming, currently scheduled for Q1-Q2 2023 which would allow you to access form content. Regarding 3, you could do this with multiple sections and repeating the field but set the select options based on the other field. Maybe not an…

No, not for a team-managed project...

Team-managed projects doesn't allow you to set conditions in the workflow, you can only do that in company-managed projects.

@Joe Giglio Welcome to Atlassian Community! You can change the condition so it is set "Any of the following condition" instead of the default all:

The instructions you found only applies to JSM Data Center, for Cloud you have to follow the instructions in this KB.

When you make a change to the SLA it will only apply to issues that are currently active in that SLA, so for example if you change the SLA for time to resolution it will only affect issues that have not yet been resolved.

You can use the CHANGED operator to do this, similar to this: status CHANGED TO "Done" BEFORE endOfWeek() AFTER startOfWeek() Or if you want to define the dates you do something like this: status CHANGED TO "Done" DURING ("date1", "date2")

Unfortunately there is no option to control where those fields are showing up...

Yes, if you go to board settings you can change the card layout. You can add up to three fields that you want to see on the board.

The renderer is controlled by the field scheme that your project is using. Go to project settings > fields and then click the pencil up in the right-hand corner. From here locate your field and then click on Renderer and then select wiki style renderer:

It should be instant. I just tested it again:

You can learn more about using smart values in math expressions here.

Yes, you can do that using automation. It would trigger on field changed and then you can use smart values to increase the custom field, like this: {{#=}}{{issue.My Number field}} + 1{{/}}

It's because the way you ave constructed your JQL, currently is is set to look for incidents with the org set to internal OR any issues with org set to charty and with the impact set to Extensive/Widespread. The OR in your JQL is the important part, and you have to use () to get the right result. Your JQL should look like…

If you have the hierarchy set up the way you want it then you can use the field called parent link to set up the relationship between epic and theme. It is not added by default to the screen, so you have to do that in order to see that field.

The short answer is no, you cannot control where the status is displayed on the board.

You would need to undo your change, or at least add back the issue types used by Xray, and then find all the issues that were changed to task and move them back to the right issue type.