John Funk Community Champion

Hi Christian - Welcome to the Atlassian Community! Yes, all statuses fall into one of three categories - To Do, In Progress, or Done. Only those categories are allowed and each status must be associated with only one of those. So if you use the same status in another workflow, it will automatically show as that same…

Hi Shasheekant, Here is an article to help guide you on how to do that. https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

Hi Filipe Is this Company-managed project? If so, yes, you can use the Issue Level Security. Or is it Team-managed? 

Awesome - I have voted for it!

Great! Glad to hear. 

Hi Mihai - Welcome to the Atlassian Community! I suggest you give it a shot first and then post a screen shot of your rule if you need assistance. 

Hi @CEO Max - Welcome to the Atlassian Community! Nope, if it is locked, it is locked. 

And incognito?

Hi Niklas - Welcome to the Atlassian Community! Yes, they will remain the same.

There's your problem then. Someone has created another field with the exact same name. You should change the name of the one that was not the original one added by Atlassian. 

Where did you go @Moon ?

Great! Happy to help.

Great!

Hi Colman - Welcome to the Atlassian Community! Make sure the Parent field is on the Edit screen. Then you should be able to click in the field and select the new parent. 

Hi Ziv - Welcome to the Atlassian Community! If the issue types use different workflows, you will need to do a Move action instead of change the Issue Type. 

Hi Athithya - Welcome to the Atlassian Community! There isn't a concept of folders in Jira. What exactly are you trying to accomplish? 

Hi Prem, Yes that is how it works if you do not use the IF/ELSE conditions. You will need to replace each one of the IF conditions you have now by starting with an IF/ELSE condition. Then you can move the Actions under each of those. 

Hi Marta, Click the 3 dots next to the field and select Copy from. Then change the bottom field to Reporter.

Hi Omkar, This is probably due to using Team-managed projects when the same name exists for multiple custom fields since the projects are all independent. If you go to Settings > Issues > Custom fields, can you verify if you see 1, 2 or no fields by that name? 

Hi Archit - Welcome to the Atlassian Community! 50 is going to be the limit of showing results at one time in a dashboard. You might consider breaking it up into two different sets of results using two different gadgets with two different filters. 

Ah, it's a labels type field. The answer would be to use wildcards, but that's not available either! You can vote for and follow that request here: https://jira.atlassian.com/browse/JRACLOUD-23038 Here's a solution using ScriptRunner if you have that. Or desperate enough for the need to add the app.…

Hi Roger, You might try adjusting your board filter to also exclude those issues.

Hi Kate, Make sure that the issue type of the parent is included in the Issue Type Scheme for the project of the new issue you are creating.

Hi Emmanuel - Welcome to the Atlassian Community! You won’t be able to create custom buttons like that. But these are steps in your workflow, and are available when you click on the status of the workflow on the issue.

Hi Bernard, Have you tried with a different browser? Or with Incognito mode? 

Correct. 

Great! Thanks for the clarification!

Hi @Eric Zheng - When you say that "default view for the project" can be set, what does that mean specifically? Does that mean that the project admin can set a global set of columns now for the List screen? Or does it just mean that the global list of menu options across the top are set for everyone? Thanks for this!

Hi Dirk, You are referring to the Issue Layout that can change. To edit the Create screen, you will need to be a Jira Administrator. If you are that already, then got to Settings > Issues > Screens and search for the screen you want to change. You can only change the order of the fields on the Create screen as there are no…

Hi Mansi - Welcome to the Atlassian Community! I think the basic problem is that there are cases where the Assignee field is empty. So the way we solved that before is to create an IF/ELSE for each scenario - Assignee is empty and Assignee is not empty. Put the current Send Email under the one where Assignee is not empty.…