John Funk Community Champion

Hi Martina - Welcome to the Atlassian Community! How are you doing the clone? 

Hi Mona, Pretty sure you can't change the Color for Team-managed projects. But you should be able to for Company-managed project Epics. 

Hi Benjamin, You would be able to a drop down to control which tasks get created unless you do that by Project Category. Create an automation rule based on Project Created. Choose the type if it applies. Then add a Condition for {{smart values}} condition. For the First value use: {{project.projectCategory.name}} equals…

Hi Petar, Sure, you can do that. Create an automation rule base on an Issue Created. The add a condition where Issue Type = Story Then add an action for lookup issues. Use this for the value for the lookup issues: parent = {{triggerIssue.parent}} Then add an action for Create Variable. Variable name: TotalAssets. Smart…

Hi Bradley - Welcome to the Atlassian Community! If I am following you correctly, you can probably do this. Create a project ( use Software Development, Kanban, Company-managed). Then create all of the custom fields where you are capturing the data. Be sure you use number type fields where appropriate, like Unit Price and…

Hi Usman - Welcome to the Atlassian Community! You should open a support ticket with Atlassian to see if the email address is on the Suppression list. https://support.atlassian.com/contact/#/

Hi David - Welcome to the Atlassian Community! Never heard of that. You should go ahead and open a support ticket with Atlassian for that one. https://support.atlassian.com/contact/#/

Hi Carson - Welcome to the Atlassian Community! Not sure if this solves anything or not, but Epic Link has been replaced with the Parent field. Maybe test it out with the value in the Parent field and see if that changes anything. 

Haha - happens to all of us. Glad you got it worked out. :-)

You still can't migrate a Team-managed project to a Company-managed project configuration wise though. 

Yeah, sounds like (and looks like) you are on DC. You can still post here, but when you post, let them know it is Data Center. So, that means that some things will be different. Not sure of everything. In this case the Smart Values thing is the branch. You can probably get by with a different Branch type. Maybe use the JQL…

Hi Insha - Welcome to the Atlassian Community! What is the purpose of this? A read only field that doesn't allow any value to be entered on a Create screen? Sorry, but that doesn't make any sense to me.

I do not use that app. You would have to check directly with the vendor. 

Also, your screenshot shows the View screen, not the Create screen. 

That doesn't line up with other fields either. Also, you have a different Default screen than any of the other 3 screens. Not sure that affects anything, but you probably want to clean that up anyway. Maybe use the Create New screen for that. Also, have you check the Issue layout for the screen? That tends to be more of…

Hi Nils - Welcome to the Atlassian Community! It's probably best for you to go ahead and open a support ticket with Atlassian to get their answer. Please post back here with what the say/resolution. Good luck! https://support.atlassian.com/contact/#/

Oh, I also see that you are using a Free subscription. Is that the case? Because you cannot configure any permissions in the Free version, including Issue Level Security. https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-free-jira-cloud-plan/

Hi Denize - Welcome to the Atlassian Community! Have you also added the field to the actual screen in the screen scheme used by the project? Not the Issue Layout, but the screen (Settings > Issues > Screens)

Hi Elliott, I am not sure of what all is available with Automation rules in DC, though I am not sure that you are. You mention 912.1 but then the question has a tag of Jira Cloud. Regardless, this is how it can be done in Jira Cloud.…

Fields do not get migrated. Those custom fields have to be already existing in the target destination or the values in the Team-managed custom fields will not get migrated into the Company-managed projects. 

That seems very unlikely. I have never known a post function to fail. Can you share the history of the issue after it was moved to Done? 

Hi Hiya - Welcome to the Atlassian Community! You should create another rule based on a Scheduled trigger that will check that each day. 

Are you talking about issues that had already been moved to Done before you added the post functions? Or are you saying even after adding the post functions, the Resolution field is not getting set? 

You can add another board for the project by following this guidance: https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

That link does not apply to Team-managed boards created with the project. 

Thanks. Can you post a screenshot of the screen with the list of fields on it (the configuration)? And then a screenshot of the actual issue on the screen that shows the field?

Hi @thumuluru.shreya - Welcome to the Atlassian Community! See if this previous post helps you: https://community.atlassian.com/t5/Jira-questions/Automatically-Increment-and-Decrement-Custom-Field-on-Transition/qaq-p/1973553

Hi William, See if this article helps you: https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

Hi @PLaksh11 - Welcome to the Atlassian Community! You might try the ScriptRunner Behaviours app. That's the only one I know that might come close. 

Hi Dwike, You have multiple transitions going to the Done status. Are you sure every transition has a post function that sets the Resolution? And are you sure you have published your workflow? :-)