Mikael Sandberg Community Champion

@Sergei Troshin The Itself transition is a circular one, it will not allow other statuses to transition to that one, which is a different setting in the workflow.

Hi @Super Diego Welcome to Atlassian Community! In order to add a global/any status transition, go into your workflow and select the status you want any status to be able to transition to and select "Allow any issue in any status to move to this one".

Currently this is expected. Idea templates are only available when you are in the JPD project because they are built on top of the item type.

Assets is only available if you are on the Premium plan or higher. If you are not on premium currently, you could sign up for a new instance and try out the premium plan, that will give you 30 days to created the demo.

@Noah Dinlemez That is a new feature that was announced in this article. 

@kwiscion Please report it to https://www.atlassian.com/trust/report-abuse and they will take action on it.

Hi @Veve,Edward, Welcome to Atlassian Community! Have you tried using the username or email address as specified in the guide you linked to? Reporter reporter Username 'admin' or 'sam@atlassian.com' To have the reporter field default to the currently logged-in user, the user must be logged in and must not have the Modify…

Besides checking the board settings, also check the filter that the board is using to make sure it returns the work items that you expect.

Yes, and by default when you create a work item an email is sent to the reporter, assignee, and watchers. If you want it to be for a specific situation you can use automation to send an email if the work item has a specific attribute.

Yes, that is possible. If you go to Automations and check under the Templates tab there is a rule called Resolve issues due to inactivity that you can use as a start. Just change the transition step to instead send an email/notify the assignee.

The short answer is no, Atlassian Intelligence is only available in Cloud.

No, it does not add the project lead to any permissions, you could specify a lead that do not have access to the project at all potentially. It is only used as "primary contact" and default assignee if that is set.

The reason this happened is because the association to screens are shared across all field configurations. It is controlled from the field, not from the field configuration. So if you remove a screen in one field configuration it affects all of them. This is a good overview of how it is all tied together, it is from the DC…

Hi @Scott Baitz, Welcome to Atlassian Community! You can use the Project Lead to auto-assign new work items to them, similar to what you can do with Component Lead. In most cases you leave the assignment part as unassigned and in that case the lead would be the person that is responsible for the project. 

Yes, it will work with any work item types. In the automation you define what type the work item should be in the destination project, and it can be totally different then the item type you use in the JSM project.

Yes, that is possible and you would use automation in order to do this. At my previous job I had a JSM project just for granting access to Tableau, and all it did was creating a task in a Software project every time a user requested access to Tableau via automation and then closed the request in the JSM project.

The thing that you are missing is that you would also need work item security if the contractors should only have access to work items that are assigned to them. You can learn more about it here. You can just add them to the Service Desk Team project role if you have work item security set up correctly. If you want to keep…

In order to create multiple help centers you need to be on a Premium Plan or higher, that gives you the option to create more help desks that can look different and have separate URLs. Have a look at this KB for more information. Your other option if you do not want to change to a higher plan would be to use an app from…

The post has been moved to the right section.

And to add to @Tuncay Senturk _Snapbytes_ answer, you can find the best practices for the Resolution field here. The KB mention that you can add a transition to set the resolution existing work items, another solution that allows you to do this in bulk is to use a scheduled automation.

Since your work item is created via another automation you have to go to rule details and click the box "Check to allow other rules..." for it to work.

Currently it is not possible to set the project via a smart value as the input. You could work around it by using the web request component and use the REST API to create the work items. Another way of doing it is to use IF/ELSE condition and each one created the work item in the project that the user provided. This is…

@Darrel Jackson No, data manager should be available, but it looks like it was removed from the roadmap. It has been available since November of last year. If you go Assets you should see Data Manager as an option. If not go into Assets configuration and you can turn it on from there.

Hi @Camilo Castro, Welcome to Atlassian Community! The list of epics are based on the permission that the user have access to, so the only way to limit it would be to limit access. A workaround that I recommend is to always link work items to the epic via the board, in the backlog you can drag and drop items into the epic. 

This is expected, and your thinking is correct, the user list also contains your external customers. In order to limit the list to only certain users you can use User filtering for the custom field and either limit it to a specific group or project role.

Hi @Irfanul Karim, Welcome to Atlassian Community! Do you have JSM - Agent product access? If not, that would explain why you cannot access Request types and the Portal settings. Being a Jira admin does not automatically grant you access to JSM specific features. If you go to admin.atlassian.com and look up your account…

I would use something like this: Email LIKE "{{reporter.emailAddress}}"

You would need an app from the Marketplace in order to do this, currently this can only be done in a team-managed project. In the past I have used Scriptrunner and Power Scripts in order to pre-populate fields.

Okay, in that case you can use a lookup objects to get the user and then use the dot notation to get the Manager attribute, something like this: {{lookupObjects.Manager}}

In its simplicity the rule would look something like this: Because it is a scheduled rule you can run it anytime and then just disable it once you have run it. Note that if the JQL returns more than 1000 work items you have to limit the query or the rule will be throttled.