Mikael Sandberg Community Champion

Hi @Kristin Woodruff, Welcome to Atlassian Community! Assuming that you want to make the issue ID unique for each board, then the only way you can do that is to have separate projects. Issues are tied to the project, not the board it is showing up on. 

Correct, adding a new form to an existing request type will not affect existing requests. The only thing that would affect existing requests would be if you change the what fields are visible on the issue view or decide to remove the request type.

You can read about the change in this article, Upcoming changes to epic fields in company-managed projects and these changes started rolling out in March. There is no option to select if you want to use epic name or the summary field, since epic name will eventually go away. What you can do is create an automation that…

We are currently using Smart terms for Confluence, but there are other apps in the Marketplace that can do this as well, check the link I posted above and it should return those.

Hi @Nilda Feliciano, Welcome to Atlassian Community! Currently the only option would be to use a glossary app, but this will change once Atlassian Intelligence is available, which will have a feature that generates a company glossary based on your content.

You can use the advanced option to add/remove data from a multi-select field. For example here is the JSON I use in one of my automations that removes the user that triggers the automation from the Approvers field: { "update": { "Approvers": [{ "remove": { "id":"{{initiator}}" } }] } } You can learn more about in this KB,…

@Trudy P Claspill That was not my interpretation of the requirement, but if that is the case you could still use conditions. There is one for separation of duties that you could utilize in that case, something like this: This of course assume that there is a transition that the assignee does before getting to the one that…

You can do this by adding conditions on the transition that the user has to be in a specific role. If the user is not in that role the transition vill not be visible to them. See Configure advanced issue workflows for more information.

You are correct, as long as the workflow is not linked to an issue type it will not affect existing issues. And the same thing applies to your screens and automations.

@Joost van de Vijver You have to use the markdown format to add a link, like this: [Atlassian|http://atlassian.com] You can learn more about the markdown text here. 

@Valter Cardoso I would make sure that the epic name and the summary are the same, and you could do that by running an automation that copies the epic name to summary. There is no option to say that it should display the epic name instead of the summary.

Hi @Courtney Lim [X], Welcome to Atlassian Community! What report are you looking to create? Do you want to report on data within the form? Currently that is only possible if you map the form field to a Jira field. Atlassian is working on an API for forms that will soon be available, according to the public roadmap it is…

Nice!

Nice explanation!

Nice! Looking forward to it!

If you go to Project settings > Workflows you can see the workflows that each issue type is using. The issue type shown in the move screen is based on the current issue type, it does that because Jira doesn't know if you are moving to the same issue type in a different project or you are changing the issue type within the…

Hi @Tyler Park, Welcome to Atlassian Community! You cannot use an app to add new custom attributes in Assets. Is there a reason why you cannot use a text, integer, or float type to record the cost?

You can check the size of the {{lookupIssues}} to see it returned any issues or not, that way you can indicate in your email if zero issues are returned. {{lookupIssues.size}} will give you the size that you can then use in an if/else component.

Hi @Kashmira Shukla, I tried to enroll to the course but get this error message after logging in to Atlassian University: Activity Locked This activity cannot be accessed from your account.

My bad, you will get a warning if you reuse the same name

You could try and access it via <slack workspace name>.halp.com, that should take you to the Halp backend and you can see the CSAT if you go to reports. 

This is expected behavior if the issue type you are moving from and the issue type you are moving to are not using the same workflow. In that case you have to move it since Jira will need more information before it can change the issue type.

You will get a warning if you are trying to create a second project with the same name as an existing one. And if you are trying to reuse the project key you would have to move the existing project to the trash and then permanently delete it before reusing it.

Hi @Adam Dooley, Welcome to Atlassian Community! Currently the satisfaction report that the user leaves via Assist stays within Assist and is not moved into JSM. All of this will change with the new Virtual Agent that is coming (currently scheduled for Q4 2023) and will replace the current Assist. In the new one you will…

Parent link and Epic link are being replaced by parent, and it looks like this change that is currently rolling out has hit your instance and that is why your automation is giving you this error. You can learn more about the change in this article, and if you go to admin.atlaissan.com > Products > Product updates you can…

Yes, that is possible. If you are using the pie chart you can change the statistic type to be for labels. But I would recommend that you use components instead, and the reason why is that labels is a free text field so you could end up with a misspelled one. Components are predefined in the project so you can avoid that…

This is pretty simple to do with smart values, in it's simplest form the automation would look something like this: I would recommend that you take a look at Smart values in Jira automation, it has examples of what smart values you can use and there are also example of how to use them.

Hi @Mark Stephan, Welcome to Atlassian Community! This is not possible to do in default JQL, since it cannot do nested queries. You would need an app like Enhanced search, JQL Tricks or any of the other apps in the Marketplace that extends JQL to do this.

You can use a JQL similar to this: (key >= IOS-1 AND key <= IOS-999)

To turn off the customer notification when the request is created, go to Project settings > Customer notifications and disable the Request created like this: The solution @JM Perrot suggested will only turn off the internal notification, the notification scheme does not affect customer notifications in JSM.