Mikael Sandberg Community Champion

Hi @Terrence Martinez, Welcome to Atlassian Community! SLAs are controlled by the status of the request, so in order to stop the Time to first response SLA based on on a custom field your automation would have to transition the request to a status that stops it. Assuming you are using the standard SLA settings, the…

There is currently an active incident that is caused by AWS that affects Trello functionality, see https://trello.status.atlassian.com/ for more information.

You could add their group to Product access if the default one gives you access to all projects.

Hi @Megan Harrison, Welcome to Atlassian Community! In order for those users to see the board you have to assign them a Jira Software license, In the screenshot you included above they only have site access, but not Jira Software. 

Have a look at the field configuration scheme for stories and see if story points is set to required, and you should also check the workflow used by stories to see if you have a validator on create that makes story points required.

@Sussi Åström In that case you could use if/else conditions to set the affected services based on the components. Just be aware that Automations have a 65 components limit, so if you have more than that then you would have to have multiple rules.

How about {{webhookData.fields."Last Name"}} and {{webhookData.fields."Hire Date"}}? Basically you have to figure out the data coming in, {{webhookData.fields}} should give you both values you are looking for based on your log.

You could do this with automation and Assets. I do this for promotions and transfers, based on the department we have different people that needs to approve. I then have an automation that sets the approvers by looking up the department in assets to get the approvers.

Your incoming variables has spaces in them so try this to get the last name and hire date: {{webhookData.Body."Last Name"}} {{webhookData.Body."Hire Date"}}

The "Impacted Configuration Items" would be the key in Assets, not the name you see in the issue. So if you want to search on the name in the AQL you would have to change it to Name in {{"Impacted Configuration Items".name}}

You could use automation that sends the notification to the customer when the issue is created. The smart value for the URL is {{issue.url.customer}}.

@Sussi Åström Have a look at this KB, all you would do is change the lookup objects to use the components field to find the object.

Restricting who can assign via the permission scheme would not solve it, unless you only want a specific user to assign all the issues. Instead you should educate your users to not reassign without a warm handoff. And if it happens then have the new assignee kick the issue back to the original assignee. You could also…

Hi @Hashim Bukhtiar, Welcome to Atlassian Community! JSM has a Customer notification feature and and one of the notifications is exactly what you are looking for, it sends an auto-reply to the reporter with a link to the request, so there should not be a need to set up something separate.

Jira Cloud does not have the "Filter Columns" feature that Seif is referring to, that is only available on DC. So you would need to get one of the many apps in the Marketplace that allows you to create custom reports.

So the folders/queues are controlled by a filter that determine in which queue the request ends up in. So you could create a new queue for these email requests and then configure the filter to something like this: summary ~ "\"<The summary that should be filtered>\"" And then in your queue for open requests, just add…

Are you trying to migrate your free instance into your company's one? If so, have you considered using the new cloud-to-cloud migration? 

Yes, that is my understanding of this new option. This is from the documentation: This is the most locked down permission setting. No one can invite anyone or request access to your product, regardless of your approved domain settings.

Check the groups that you have assigned to your products. For example if jira-software-users is the default group that gives you access to Jira, and it also listed under JPD as one of the groups, the user will get both.

Just to add to @Ignacio Vera answer, product discovery will not prevent a managed account from creating a new site, but as a site admin you will be notified when that happen and can take the appropriate steps.

Hi @Kaleb King, Welcome to Atlassian Community! One option that comes to my mind is to use user properties to set the preferred communication channel, something similar to this article that sets the user's Slack ID as a user preference so you can send them a DM via automation. You could have a Communication Channel request…

Forgot to add that this only applies to company-managed projects. If you are in a team-managed one you would have to enable Sprints by going to Project settings > Features.

Hi @Arda Isiksalan, Welcome to Atlassian Community! Moving from Kanban Board to a Scrum board is easy, and you could reuse the same filter that you currently have for your Kanban board is you like. All you have to do is create a new board by clicking on the down arrow to the right of your current board and then select…

Currently the only thing you can do is turn off that feature, or limit it to specific products if you go to admin.atlassian.com > Products > User access settings. A possible option if you want to get notified would be to create something that uses the Cloud admin API to compare the list of users between runs.

Great write up! Thanks @Rex! 

Is customfield_10121 a single user picker field or multi-user? If it is a user picker field then you do not have to add .accountId when you set the smart value, that field will store the accountId already, but what you see is the display name.

Could it be that the done issues were moved to that status outside of a sprint? Look and see if the sprint field on those are empty, or if they are in a future sprint check the history to see if they moved to done before the sprint was added to the issue. I would also consider redoing the filter that you have on the board…

In order to copy users from one user picker field field to another you have to do it one user at the time. So in your automation add an Advanced branching and set the smart value to the first field, and then edit the second field using this JSON: { "update": { "customfield_10120": [{ "add": { "id":"{{smartValue}}" } }] } }…

Hi @Monica Brazelton, Welcome to Atlassian Community! When an issue is moved to Done status, are you also setting the Resolution field, either as a post function in the workflow or via a transition screen? The resolution is what Jira is using the determine the issue's lifecycle status. If the resolution is not set that…

You should be able to do this using automation, and the Get users in organization endpoint to see if the request participant is part of the org, and set the rule to trigger on changes to the Request participants field.