Mikael Sandberg Community Champion

Assuming that you just enabled the automation from the library I would try this. Go to the transition steps and reselect the status you want to move it to, hopefully that will help.

This is awesome @Brittany Joiner! I won't be able to join the release party but I will definitely make sure to mention the book, newsletter and the youtube channel to my users that are migrating to Trello in a couple of weeks. 

In JSM you have to go to the issue view in order to see the new JQL editor, you cannot use the View all issues search to see it. From your queue, click on the issue view icon up in the right hand corner and from here you should see the new editor.

Hi @yousefq Welcome to Atlassian Community! Have a look at this article, How to create dynamic looping in Automation for Jira, it describe how you can do this using two automation rules and using dynamic values. 

The mapping of the statuses to the columns is what controls what you see both in the backlog and on the board. You can map multiple statuses to a single column like this: See the mapping as a way of filtering your issues, unassigned statuses are invisible to the backlog/board. Yes, when you change the workflow and add a…

You can't. In order for them to show up in the backlog the status has to be assigned to a column. But they will not automatically show up on the board just because the status is mapped. Once you map the status, the issues will show up in the backlog and only issues that have been added to the board will show up as you can…

Is the resolution field set on the missing issues by any chance? Or do you have any unassigned statuses? For the resolution, just go to Issues and check the Resolution column, if it says Unresolved they should show up on the board.

Hi @Ardis Ramey, Welcome to Atlassian Community! When you enable the backlog it will not show up as a column in TMP, instead it will show up on the left hand side as it's own menu. It is only in a company-managed project that you would see the backlog as a column when configuring the board. You should see something like…

You need to look at how your SLA is configured, and especially the "Finish counting when..." section. The default one looks like this and stops the clock when a comment to the custom is added, status is changed or the resolution is set.

You cannot use an inactive workflow in a team-managed project. The way you modify the workflow in a TMP is to click on the three-dot menu on the board and then Manage workflow. From here you can modify the workflow the way you want it. Please note that this would also change the columns on the board since they represent…

You may want to take a look at Atlas which allows you to share goals and project updates between teams. We are currently planning on moving away from Asana to Jira and Trello and Atlas will play a big role in that for project updates and reporting.

Hi @Previously Louis Forte Now Ben Karlin since oct 10, Welcome to Atlassian Community! The Any domain is a default setting and is there so that non-public email domains gain access if you allow that. This cannot be removed, but you can remove what products they can request access to. You can learn more about it in this…

If you are on Windows there is the enterprise version of Sourcetree that you can use to install it.

Just to add to @Marcus Jones answer, I would trigger on field value changed because the form may not have been added when the issue created would trigger. Also note that there is an API coming for forms that would allow you to bypass using a custom field to store the answer, instead you can use the API to get the answers…

Create a global automation that triggers on Issue moved and then use the Edit issue component to clear out the sprint field. In it's simplicity it would look like this:

Are you looking to remove the customer from accessing a project or are you looking to completely remove the customer from your instance? If you just want to remove access then go into Project settings > People and remove the customer from there. If you want to completely remove the customer from the instance you need to…

Hi @Jaroslav Jasek, Welcome to Atlassian Community! Have a look at your board mappings, each status is mapped to a column on the board, and in this case it looks like you mapped Done status to your To Do column. Just click on the three-dot menu on the board and select Columns, from there you can do the mapping. 

I think that document format is only for Jira Software. Assuming you are using the JSM create customer request endpoint you would not need to define the document format if you look at the documentation for it.

Yes, the resolution is an important feature in Jira and tells it if the issue/request should be considered closed or not. Please have a look at Best practices on using the Resolution field for more information. To fix your existing requests you can create a scheduled automation that selects all the closed issue and then…

You would have to remove the sprint from the sprint field on all the issues that were moved from project A to project B in order to clean it up. And I would recommend that you set up an automation that clears out the field going forward when moving an issue between projects.

Hi @Slava Kovelman, Welcome to Atlassian Community! Please forward the email that you received from that project to https://www.atlassian.com/trust/report-abuse and that team can take action on it.

Also check your workflow to make sure that you do not have a condition on the transition to done that prevent you from moving it.

Hi @Stella Griffith, Welcome to Atlassian Community! What type of project are you using, a team-managed or a company-managed one? If you look on the left at the bottom when in the project it will tell you. If it is a company-managed project, check that you have the right permissions in the permission scheme to transition…

Hi @Sibyl Weng, Welcome to Atlassian Community! On the closed requests, do they all have the resolution set? If the resolution is not set Jira consider the request to still be unresolved and would then show up as an open request. 

Currently it is not possible, unless you where added to beta before Atlassian halted the rollout of public links. Currently it is on track to be released in Q4 2023 based on the public roadmap.

The "Create child issue" button that you see when going to the epic do not check the hierarchy, it behaves the same way as if you would click create issue in a board or use the Create button on the main menu and show you all available issue types (except for sub-tasks) in the project. The hierarchy check only happens after…

Okay, so using the "Create child issue" does not check the hierarchy that you have configured, it will behave the same way as if you are on a board and click create issue or use the Create button at the top menu and it will show you all available issue types in the project (except sub-tasks). It is only when you click the…

It sounds like you have configured your workflow to automatically transition on 1 approval instead of all. Here is what I would do. I would update the workflow so it requires two approvals and then have the automation trigger on the transition to the approved status to add the comment for the customer.

Hmm, the web response should already be a JSON format, based on the screenshot you included above it is coming back as a JSONStringify format. So that leads me to believe that when you are using it in the custom data field it is missing a character. I would recreated the data in a JSON parser to see what could be wrong.

You cannot create an initiative as a child of the epic if you add it above the epic. We have a similar hierarchy with initiative - roadmap item/milestone - epic - story - subtask, and the way you link your epic to either one of them is by going to the Parent link field to select the issue the epic is linked to.