John Funk Community Champion

Hi Annick - Welcome to the Atlassian Community! It might be because you have more than 1,000 Story issues that your are converting. I would do a bulk change first on 900 or so of them. (or all of them) And then try to your switch again. 

I would take a look at your automation rules then as one of them is probably not set correctly. 

Hey Shawn, How are these tickets cloned? Manually? By Automation? Workflow post functions? When you look at the history of one of the tickets, who does it say is moving the ticket to the status? 

Obrigado por compartilhar. Isso parece ser um bug para mim. Eu enviaria um tíquete de suporte para a Atlassian. https://support.atlassian.com/contact/#/

Hi Andy, You must have the Jira Administrator or Jira System Administrator global permission to archive or restore projects. You must have the Administer Jira global permission or you must have the permission to administer projects to move projects to trash. You must have the Administer Jira global permission to delete…

Great to hear!

Hi Edwin, Actually, you can go edit the workflow and choose the Text option instead of the Diagram option. You can see the transition ID there - it's usually a simple 3-digit number. 

Hi Minori - Welcome to the Atlassian Community! Check the Permission Scheme for the project you are working with. The user should have permissions for Work on Issues under Time Tracking section. And permissions for Create Attachments under the Attachments section. 

Hi Iana - Welcome to the Atlassian Community! Can you share the rule that you have so far? 

Olá @cleider trindade ambrósio - Qual personagem você está usando para dar o erro?

Hi Yasin - Welcome to the Atlassian Community! Go to the Global Configuration for JSD projects here: https://yasinkeles.atlassian.net/secure/admin/SDConfiguration.jspa

Hi Behara - Welcome to the Atlassian Community! No, that is not possible. An issue type can be linked to one and only one workflow on a project. And it cannot be dynamic - it is the same workflow for all issues for that issue type. 

Yes, I didn't realize that it would be limited to one project. I don't know what you cannot do a combination of Project and Issue Type for for the same project - that's a real drawback. 

Hello and Welcome, Raymond! We are glad you are here!!

Hi Andreas, Yes, you can do that by adding different Contexts to the custom field. Go to Settings > Issues > Custom Fields Search for your Custom Field Click on the ellipsis menu (3 dots) on the right hand side and select Contexts and default value Then click on Add new context link There you can create a new context and…

@John McKiernan 

That's very baffling! I would open a support ticket with Atlassian. https://support.atlassian.com/contact/#/ Please post the solution back here so we can close this one out. 

Hi Darrel, It's just a board, so I would say give it a try. If it doesn't work, just delete the board. Just make sure you have all of the statuses for each workflow mapped to the columns of the board. 

What's another issue type that would apply? And have you run the query just for that issue type? (Replacing Bug with that issue type).

You can't. 

Merged and Open are not the same status for pull requests. Merged is not Open. And you can't say < 0 - that won't return you anything. You can use > 0 

I don't know - I would open a support ticket with Atlassian. :-) https://support.atlassian.com/contact/#/ Please post the solution back here so we can close the ticket out.

I can confirm that it defaults to Order by Created. And when I change it to Order by Priority and then leave can come back, it changes back to Order by Created. But I do not know if it has always been that way or just recently started - sorry. 

Thanks for the clarification. I would run the query in JQL advance search to see if it returns a value there. Modify as necessary until you get the results you expect to see, then paste it back in the rule. 

Hi Christophe, This is certainly possible using Automation For Jira. Here is some more information about the tool to get you started. Once you have a rule created, post back here for any additional help you might need. There are two types of automation: * Global: In the Free version, you get 100 executions per product, per…

Hi Conrado - Welcome to the Atlassian Community! Why do you have a check on the issue key? It is already only dealing with a single key. I would take that part out and see if it works for you. 

Hi Srivastava - Welcome to the Atlassian Community! Are you the only one performing these tasks? Or are there multiple people working on them? If just you, then you can handle it with a single project and use components to keep each issue categorized. If multiple people, I would create multiple projects. 

Hi Nodar, Do you the value of the options for a pick list? Or the actual saved value for the field in an issue? And is this a Next-gen project? Or Classic Software project? (Or some other type).

Hi Aleksandr, You cannot directly change the workflow for Next-gen projects. You can only add columns to the board which modifies the workflow.

Do an ORDER BY KEY asc