Mikael Sandberg Community Champion

Hi @Kelli Wisuri, Welcome to Atlassian Community! What you see in the Backlog view is the name of the columns, not the statuses. If you look at the number of issues listed in the backlog that corresponds to the total number of issues in the backlog column. Same thing with the In Design, that is the column name, so if you…

It can be done via automation. Are the fields in the form linked to Jira fields or do you just want to attach the form to existing issues? To just attach the form to existing issues is simple, just create a scheduled automation and use the Attach forms component. If you want to populate the form with linked Jira fields…

Hi @jonah_grotz, Welcome to Atlassian Community! Are the tickets using the same issue type/workflow?

Hi @Shelton Adams, Welcome to Atlassian Community! What platform are you on, Cloud or Data Center/Server? I know on DC when making changes to an existing workflow it may not be fully published and could then lead to situations like this. In order to solve it you can make a copy of the existing workflow and then go to the…

Correct, in order to create the global/custom field you need to have Jira admin permissions. Also note that not all custom field types can be used in a team-managed project, for example Assets fields are not supported. 

Hi @Dan Huston, Welcome to Atlassian Community! Team-managed projects now support global fields i.e. custom fields that you have created for company-managed projects, and you can add multi select fields that way. Here is an example of a multi select that I created and then added to a team-managed project:

Yes, this can be done with automation and smart values. The smart value for replacing ISNT with TKC would look like this: {{issue.summary.replace("ISNT", "TKC")}}

Hi @Sofia G, Welcome to Atlassian Community! In order to modify any fields on a request after it has been submitted you have to have a JSM license and be an agent in the project. A way to work around it is if you add a form as part of the approval, add the approver as a request participant, and then have the approver fill…

Yes, since you are in a branch the focus is no longer on the issue that triggered the automation, so yes you would be able to edit the linked issue and set the label.

Hi @Matias Coaker, Welcome to Atlassian Community! Are you using a branch to get to the linked issues? Your automation should look something like this:

The filters that @Joseph Chung Yin included below should give you all issues no matter if they are resolved or not. If you only want unresolved issues then you can add resolution = Unresolved to the filters and that will do it.

Instead of using a separate status for duplicate you could use Resolution, that is what I use in the example automation above. 

It would look something like this: This example is looking for issues with the same summary and if the returned lookup issue size is greater than one it will close those other issues.

Yes, that is possible to do with automation and I would use the SLA threshold breached trigger and set the priority that way base don the age.

Hi @Patrick Costello, Welcome to Atlassian Community! Yes, this can be done by setting a condition on the transition in the workflow and it can be based on the user's permission in the project if they can transition to that status or not. If they do not have permissions to do it, they will not see the transition as an…

Hi @Toni Tabieros, Welcome to Atlassian Community! What report are you using? The Reports section in JSM allows you to create custom reports which can be used to report on open and resolved requests. You can also create your own filter that would show open and resolved requests per assignee/agent.

Did you test it with your own account? The default is that you will not get notifications when you make the a change to an issue, but you can always change it by clicking on your avatar and select Notifications.

Hi @Snorre Strand Asbjørnsen, Welcome to Atlassian Community! If you @ mention a user in the comments they will be notified via email that includes the comment and has a link to the issue. They will not get any other notifications about the issue unless they are added as watchers. 

Hi @Maxi Romero, Welcome to Atlassian Community! Both of these things can be done from Board settings. From here you can modify card layout and card colors. Have a look at this KB for more information. Please note that this only works if you are in a company-managed project, team-managed project do not have these features.

Is the users customers? If that is the case then you could use details fields to do this. If they are actual users then you have a couple of options. Assuming that you do not integrate Jira with an identity provider then you could use user entity property to set the manager.

You can do this via automation and smart values. The smart value would be used to extract information like license plate and workshop, then use that as part of a lookup issues to see if it returns more than one, and if that is the case close the duplicate issues.

You can find tutorials here, and the documentation is here. It should be fairly straight forward automation to create, it would first extract the information from the request, like the email and this can be done using smart values, and then use a web request component to make the API call to AD. The documentation has a…

If you are looking for an app from the Marketplace then Multiplier should be able to do this for you. Your other option would be to use automation and web request to AD to create the user and email.

Short answer is no, you cannot add multiple no one users, unless you create a user for it, but then you also have to give a license to that user. 

Make sure that the copied ticket has the request type field set, that is what controls if the ticket is visible from the portal or not. You cannot set the request type as part of the create issue in the automation, you would have to use a branch and set the request type Or use the new Create issue with a request type…

Hi @Merrin Fulton, Welcome to Atlassian Community! Currently it is not possible to name your branches. The way I work around it when I have a lot of branches is that I add a Log action component at the top of the branch so I can identify it that way. 

No additional API calls or set ups are need, post functions are a Jira out-of-the-box feature. Here is an example and you can see that one of the options is Update an issue field. That is the rule used to update the resolution field. Now, there are apps that extends the default rules by adding their own ones, like for…

The most likely scenario is that Whiteboards will be Confluence Cloud only feature. The code base is completely different between Cloud and DC.

That is a good question. If you go to Project settings > Customer notification there is one for Participant added, but I am not sure it that one is triggered only after the request has been created or not (I haven't tested that yet). My guess is that CCd users get the Request created notification and if that is the case…

Jira project admins only get elevated permissions within the project, they will not be able to remove filters that they are not the owner of nor will they be able to delete projects. All they will be able to do is administrate some features within the project like changing the issue layout, adding/removing access for users…