Mikael Sandberg Community Champion

In the JQL that is being used by the automation, just add statusCategory != Done to it and that will exclude any issues that are in a Done status (green color if you look at the workflow).

Are you using automation to send the email or are you referring to the customer notification? If it is an automation then you have use {{issue.ORG-ID}} in the email body.

startOfDay() is using the timezone that is set on your account, so if your account timezone is PST then that is what startOfDay will use. You cannot define the timezone in the search, you would have to change your account's timezone in that case.

Just create a group in Jira and then add the users that should receive the email to that group. Then in the automation you can use that group in the to field like this:

What you see is expected behavior. You should not have estimate on subtasks, that stays on the story level, all based on scrum principals and that is what Jira is following. You can see further explanations in this thread. It is only time tracking that will roll up to the story from subtasks.

Changing the screen will not affect existing issues other then that fields that are currently available may not be visible after the change, but the data is preserved. The only time data is removed is when you delete a custom field. In order to make sure required fields are not removed you have to look at your field…

Hi @siri g, Welcome to Atlassian Community! Your issue type definition is wrong, you need to use the internal Id for the issue type, not the display name. It should look something like this: "issuetype": { "id": "10000" }, There are a couple of ways to get the Id, have a look at this KB for more information.

It is not possible, the only smart values that you can use in the email template are listed if click on insert values If you want to create your own approval notification you would have to disable the customer notification for approval required and then use automation to send it out. 

The sprint doesn't have an assignee, or team members so you need to know who to send the email to. You could do a lookupIssues and use that to send out the email. But that would generate an email for each issue, so I would probably use a group email instead.

Have a look at this KB, it shows you how the csv file should look like. Also note that in order to update existing issues you have to go to Settings > System > External System Import. You can get to the import if you are in the project and click on the three-dot menu, but that only allows for importing new issues.

It means that you do not have access to Confluence, so you need to contact your Atlassian admin to get you access to it. What you have access to is Jira. Btw, I removed the reference to your instance and your email address, this is a public forum so you do not want that information to be available to the whole internet.

On the "approval by the client" status add the approval step and set it to Jira field and Approvers and then set the transitions that should happen on approval/decline. Note that you can only add the approval step when the workflow is active. Next step is to create an automation that sets the customer to be approver once…

Okay, so that means that your project most likely is a company-managed project. There are a handful of JSM projects that can be created as team-managed geared towards Customer service, HR, Facilities, and Legal service management.

You have a couple of options. One is to add a transition out from closed that allows the customer to reopen it. Another option would be to have a status where the customer approves/decline the fix. For the first option you can add an automation that moves the request back to open if the customer adds a comment. If you look…

Hi @Chris Harris, Welcome to Atlassian Community! You cannot compare two fields in out-of-the-box JQL, you would need an app that extends JQL with a function that allows you to do that. Based on this thread it looks like Scriptrunner can do this, and you should check out all the other apps in the Marketplace that extend…

Yes, that is possible. You would do this with a combination of an issue security scheme that defines who should have access based on the level, and automation that sets the security level based on the assignee. You can learn more about how to configure it here, Configure issue security schemes.

You could also have global automations that generates these emails, and you can find those by clicking on the link while in Project settings > Automation or if you go to Settings > System settings > Global automation. Note that you need to be Jira admin in order to be able edit global automations.

It sounds like you have automations set up that sends these emails to the users based on the due date. If you go to Project settings > Automations you will see all the automations that have been created in the project.

@Patricia Francezi_iDev_ is correct, so instead of using the Field contain condition, change it to use JQL condition. That way you can search on exact phrases. summary ~ "\"1207\"" This would only find 1207, 1207-0 and 1207 0. For 207, I would use this one: summary ~ "\"207\"" AND summary !~ "\"1207\"" Make sure you test…

Hi @Tracy Collet, Welcome to Atlassian Community! The automation looks correct, the only thing that I can recommend if you want to test it out before enable it is to make a copy of it, and use the manual trigger and instead of edit issue field use the log action. That way you can go to an existing issue that have the…

Try this query instead: created >= -50m AND status != "Done" AND summary ~ "\"{{issue.summary.substringAfterLast("RealTimeDA-")}}\"" This should do the trick for you.

Those are not labels, they are the epic name/epic color that the issue is associated with. You can see and change these colors in the backlog of a Scrum board or from within the epic itself.

I reference Smart values in Jira automations a lot, and from time to time I end up in the automation template library.

Hi @Nutley_ Madalyn, Welcome to Atlassian Community! That is not a feature within Atlassian, that is either your browser or the OS you are on that does that. In Chrome there is a setting for spell check, and MacOS has similar under Keyboard. 

Use "Name" = {{issue.components.name}} instead, otherwise components would come back with the internal number instead of the display name. And to cover the situation where you have multiple components on the request you should use this one instead: "Name" in ({{issue.components.name}})

If you look on the left-hand section while in the project, at the bottom it will tell you what project type it is.

Correct, you have to do it using automation. Here is an example where the linked assets is populated with the reporter's assets when a request is created.

It is possible, our application access requests are fully automated. You need an application that can talk to both Jira and in your case Azure AD. We are using tray.io to do that, but I know that Access management for Jira can do it as well.

Hi @Amber Werneke, Welcome to Atlassian Community! You can only example text to the description field if you are using a team-managed project. This feature is not available in company-managed projects.

You can do this with automation, that is what I do with our onboarding tasks. You would need to link the field on the form that have the employee name to a Jira field, and the automation would look something like this: Note that this is a very simplified version of the automation, you want to add a condition that checks…