John Funk Community Champion

Hi Matthew, First, why do you have a transition from Abandoned to Backlog? Abandoned is a Done status category and the issue should end there. Remove that transition and your problem will be solved. :-) Second, I suspect that there might be some type of automation that is auto transitioning the issue from Abandoned to the…

Can you try to Delete the Testing status? 

What happens when you click on Edit?

Can you share the same screenshot with that other account? 

Users have the ability to decide individually what fields they see in the create screen using the Configure fields option. You can't control that. You can control what fields are even available to be used in the create process - but it will apply to all users and not just some. 

There are still Create, Edit, and View screens in Jira Cloud and with the new view. Go to Settings > Issues > Screens to create those different screens. Then you can follow my guidance above. 

It probably can - I just don't know the syntax for that. The folks with JMWE should be able to help you though. 

Hallo Eric, Ik geloof niet dat er een manier is om die nu te verbergen. Je gebruikt ook de Old Jira Issue View, die eind deze maand verdwijnt. Dus misschien wil je het eens bekijken in de New Jira Issue View om te zien hoe het er daar uitziet.

Hi Jakub - what if you went straight to the Permission Scheme? Go to Settings > Issues > Permission Scheme And then edit the Permission Scheme there. 

Yes, I can see it - thank you. What happens if you check the box next to it. Do you then see it on the Create screen? 

Yep - all depends on the conditions on the transitions. I am planning on doing a talk for the Boston Atlassian User group on April 7 on flexible workflows. I will have some graphics and things for that. Ping me after that and I can share. :-)

Hi Brett - Welcome to the Atlassian Community! Status Category is not the same thing as the Status. The Status Category has just three options - To Do, In Progress, or Done. All statuses must fall into one of these categories. So the To Do status is not the same as the To Do status category. Although it probably has that…

I have not used the Clone Epic Template app, but it might be more specialized just for Epics. Since it is Free, I would say just give it a try and see if it meets your needs. :-)

Can you share a screenshot of what you see on the create screen? Go ahead and click Configure fields first and then capture the screen that shows all of the fields. 

Hi Thao - Welcome to the Atlassian Community! Can you share the rule you have so far? Are you using the Field Value Changed trigger to start the process? 

Hi Steven, It may be possible depending on exactly what you are trying to do. Can you share more details? 

こんにちはゾーイ、 プロジェクトの作成中にAutomationFor Jiraに何を求めますか？

Hi Josef, Do you have any add-ons? I know you can do that with Automation For Jira - and probably ScriptRunner as well. 

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

I only use Cloud and it works great for me. What are you not able to do?

Well, that is a little more complicated, but basically we do have a flexible path. So Status A can go to either Status B or Status C. We control which transition they see by use a custom field that they select values for. It is a checkbox field that we call Flex Path. So Flex Path has values like Write Copy, Visual Design,…

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

You probably need to open a support ticket with Atlassian then: https://support.atlassian.com/contact/#/

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

Hi Gerardo - Welcome to the Atlassian Community! We are using Classic Software projects to do the same thing. The workflow is really long and has lots of statuses in it, but it works. 

For the branch, try using For Linked Issues instead of Current Issue. Then use {{triggerIssue.Incident Cost - Lost Agent Hours}}+{{issue.Incident Cost - Lost Agent Hours}}

Preferably the Honey One :-)

Hi Prabhu, You will need an add-on like Deep Clone to do that. 

Hi Diane - Welcome to the Atlassian Community! You should be able to go to Board Settings or Configure Board, and then to the General tab. You will need to be a Board Administrator to do that though. 

Hi Meital, Automation for Jira does not prevent any actions from taking place. That is done with Conditions and/or Validotors on the workflow. Automation rules only fire AFTER something has taken place - a field has been updated, the issue has transitioned to another status, a query was fired as a part of a scheduled run,…