John Funk Community Champion

Great! And you are welcome!

Do what you have done, except just select the field instead of More Options. Then put the values in that field. 

Then use the Regular Expression Check validator, select the field and the put the value of the field in the Regular expression. You will have to do that 4 times - one for each value. 

The issue key of the story will be the indicator for which project they came from. You can add a Quick Filter to the board also to specify the project if you like. That is what you will need to do for the Backlog to "split" the display. 

Hi Max, Check the Request Form to see if it is marked Required there. 

Hi Eric, Not sure if this is what you are asking, but you can add the Status field to the CSV file when you import. 

Hi Shelby - Welcome to the Atlassian Community! You should create a separate Screen Scheme for each Issue Type. Then update the Issue Type Screen Scheme associated with the project to match the issue types to the screen schemes to be used. Then within each screen scheme, create screens with the fields you want on them. If…

Okay, there is a lot going on there, and I am still not completely following. They appear to be multiple separate issues. So let's take them one at a time. What's one thing are trying to do and not able. Please be a exact as you can with each step - even showing screenshots if you can. 

Sorry, I misunderstood. Create a screen that only has the 4 fields you want populated. Then add the screen to the transition to Done. Then add a validator for Field Required for the same transition and select the four fields.

I would open a support ticket with Atlassian to see what they say. Please post the resolution back here. https://support.atlassian.com/contact/#/ Good luck!

Doing the field directly instead of the advanced JSON will be no more performance impacting. I would go with what works. 

Hi Ahmet, I think the problem lies in fully understanding the structure. Tasks are children of Epics. Sub-tasks are children of Tasks, not Epics. I guess you could say they are grandchildren. So the automation is only going to go one level deep. You can accomplish this by creating a second rule where the Condition is for…

Hi Shivani, This previous post should be able to help you. https://community.atlassian.com/t5/Jira-Software-questions/Automatically-Increment-and-Decrement-Custom-Field-on-Transition/qaq-p/1973553

Great! Glad to hear. 

Hi Eran, If you use Components, you could do it with the Component lead. Or you could create an automation rule or script to populate the Assignee field. Or you could add a post function to the Create transition in the workflow. 

Hi Vishnudeva - Welcome to the Atlassian Community! How are you defining that the issue is "Closed"? Is there a status called Closed? Are there multiple statuses by different names that represent Closed? Or there something else? 

I would open up a Support ticket with Atlassian then. Please post the resolution back here. https://support.atlassian.com/contact/#/ Good luck!

Hi Santhosh, I will try to help with what I can, but hard for me to do much without seeing your instance. So it might take a support ticket to Atlassian. Are you able to populate the Approvers field with the name? And how are you doing that? Are you populating it and then not seeing the name? What happens when you try to…

Hi Parveen - Welcome to the Atlassian Community! Where is it not showing up that you would expect it to? Is it a status in your workflow? Is it a field? 

The problem is that Team-managed projects are designed to be completely self-contained and not interact with any other projects - even other Team-managed projects. I don't think you are going to be able to do what you are trying to do. You would need to create a Company-managed project for JWM and then migrate you data…

Fair enough - that happens a lot. Let me research a little more and see if I can get you some better resources. But basically, you can adjust the hierarchy since you have a Premium subscription by going to Settings > Issues > Issue Type Hierarchy. There you can add levels above the Epic level if needed though I am not sure…

You should probably open a support ticket with Atlassian. https://support.atlassian.com/contact/#/ Please post the resolution back here. Good luck!

Hi Kiran, You will need to make sure the Bug issue type is in the Issue Type Schemes used by each project. 

Hi Hayden - Welcome to the Atlassian Community! Are these both Company-managed projects? If you use the Parent field on the scrum board issues, do you see the Epic from the JWM project? You will most likely need to include the Epics of the JWM project in the board filter used by the Scrum board in the other project. 

Hi Amy - Welcome to the Atlassian Community! It really doesn't matter which template you use because you are most likely going to modify it anyway. Just be sure to use a Jira Software Company-managed project. 

Hi Ryan, Where are you planning on using the sum? Is there some type of parent that you could place a custom field for "Total Dollar Amount"?

Yes, Team is a system field. Try adding it to the Create screen used by the project. Also, it will be good to hear why Atlassian support says. 

Hi Christine - Welcome to the Atlassian Community! How are you defining if a "Project" is past due? 

You are welcome.

Ah, check the Conditions on the transition in the workflow. Can you share those?