John Funk Community Champion

Hopefully some of the ScriptRunner folks on here can help you out. :-)

Hey Mark - Welcome to the Atlassian Community! That's awesome that you were able to get it figured out! 

You should be able to rename any transition. Just thought if you have done that was giving you trouble that you could recreate it. Are you not able to rename other ones either? 

Great! Glad you were able to track it down!

Great! Glad you found the solution.

Hola! ¡Bienvenido a la comunidad de Atlassian! Todavía no es posible en la nube, pero está llegando. Puedes ver más información aquí: https://community.atlassian.com/t5/Jira-questions/Archiving-a-project-in-JIRA-Cloud/qaq-p/896171

Hi Andrey - Since it is still inactive, it might be faster just to Delete the transition and create a new one. 

You are welcome - have a Merry Christmas!

Hi Ryan - Welcome to the Atlassian Community! Maybe try just connecting it to a single group that you are in and see what happens. Also, definitely check the Permission Scheme and the People settings under Project Settings. 

Hi Alex - Yes, you can control which fields are required for not only individual projects but even for the combination of project(s) and issue type(s). That's all done with the Field Configuration. You can see more here:…

Yes, I agree on the limitation. :-) 1. It will affect filters if they use the old value. Those would need to be updated to use the new values. 2. It should not mess up their format. 

That being the case, I am afraid you are not going to be able to control that. :-(

Hola David, Echa un vistazo al artículo a continuación. Debería ayudarte con la migración. Está en inglés, pero probablemente pueda traducirlo con la suficiente facilidad. Saludos!…

Hi Pooja - you might try Automation For Jira. It will not fire an action (like updating F2) until F1 is actually saved, not just updated as you click a box. But that might get you what you need. 

Hi @Oleksandr Tynetalo - my first thought is that you could put a transition screen on the Deploy flow for moving to that new status. But not sure what would actually happen during the Move function. You might want to try it out.

Hi @Shivaraj kumar - You can do that with a dashboard gadget. 1. Create a filter with all of the issues you want to see. 2. Add the Two Dimensional Filter Statistics gadget to a dashboard. 3. Use Status and Assignee as the X and Y axis as desired. I hope that helps!

Did this take care of all of your needs?

There is a Condition type called: Separation of Duties condition. Try that one out and see if it works for you. 

Hi Imran - Welcome to the Atlassian Community! Yes, you can put conditions on the transitions. It might be harder to restrict by a certain user in certain circumstances though. So, for your example it might be possible to exclude anyone that was already assigned the issue at a previous stage. The question would be if…

Hi Aaron - Welcome to the Atlassian Community! Can you share the filter you have already? Maybe something like Project = ABC and (Key != ABC-123 and "Epic Link" != ABC-123) where ABC-123 is the key of the Epic you want to exclude. Give that a try and see what happens. 

No, that's the quickest way on the Bulk Change. If the field is required, it shouldn't allow you to save with None. The other option is to also have a Default value for the field. 

Hi Hy - Welcome to the Atlassian Community! To remove the None value, you need need to make the field Required. If you want to change the value, go ahead and add the new value first, then do a bulk change from the existing value to the new value. Then go back and delete the old value. I hope that helps!

Oi Dian - Bem-vindo à Comunidade Atlassian! Isso não é possível com o Jira pronto para uso (ou até o JMWE, eu acho), mas você provavelmente poderia fazê-lo com o complemento chamado Automation for Jira.

Hi Toks - Welcome to the Atlassian Community! If there is a Default Assignee on the project, then that person will be assigned. If there is not, there will be no one as the assignee when it gets created. 

Hi Yaron - Welcome to the Atlassian Community! No, the board does not get disabled, delete or otherwise rendered inoperable. Actually, there's no connection at all between a board and who created it. Just change out the Board Administrator if you need to. 

I see an bug reported to Atlassian a while back. But they say it is fixed. https://jira.atlassian.com/browse/JRACLOUD-71485?_ga=2.77607955.625634002.1576503562-1313086432.1576012938 You might need to open a support ticket with them. https://support.atlassian.com/contact/#/

Hi Ricky - Welcome to the Atlassian Community! What is the user's status in the Site Admin (Users) section? And how many users total do you have - because I think there is a limit on the free version.

You don't have the Planned/Backlog status mapped to your board. You will need to create a column at the far left

Hi Mechelle, If you got to the Board Settings, do you have the Backlog status mapped to the Backlog column on the far left side?

Hi @neelam annad - You cannot compare two date fields in stand JQL. You would need to compare each date field to a range of values (like created >= 2019-12-01 to see issues created on or after December 1st).