John Funk Community Champion

Hi Gazi - Welcome to the Atlassian Community! Did you follow the guidance of the document exactly? You have to begin within the Service project or you will not see the trigger. 

You are welcome!

See if this helps you: https://support.atlassian.com/jira-service-management-cloud/docs/replace-the-workflow-of-a-request-type/

Hi Chris, Create a new project and give it a name with Template in it somewhere. Maybe even create a Project Category called Template to help identify these so people know not to change them. Get everything in place for all of the configurations as you want it. Then when you create new projects, create them based on this…

That's what I thought. So you go to Project Settings, Issue Types, Edit Workflow. 

Ah, so something on the JPD side. That makes sense because it is so new. Glad they uncovered that and getting it fixed. 

Great! Glad to hear. 

Hi Fernanda, Since it is cloning all of the items, I don't think there is a way to control that in the middle of the cloning process for a single field. The only think might be to edit the comment before you clone the issue. Maybe leave the name but put in a space between the @ and the name. Something like: Hey @ johnfunk…

Hi Ahmet, I don't know if a way right at the top of my head. Maybe it has something to do with the order of the Issue Types in your Issue Type Scheme - what order are they there ? And maybe the same in your Workflow Scheme. Can you share of screenshots of those?

That's very baffling since you are on a Free site and there should be no Permission limitations at all. Can you share a screenshot of your rule, especially any details related to that field? 

Hola Andrés. ¡Bienvenido a la Comunidad Atlassian! Debería poder hacer clic en los 3 puntos a la derecha del campo Aprobadores y elegir Copiar desde. Deje la primera opción en Número actual pero cambie el campo debajo a Reportero o lo que diga la versión en español.

@Liz Nixon - is it all transitions? Or just a certain transition or two? Is it all boards? Or just certain boards? 

No, you can't have two global (All) transitions to a single status. And you can't do what you want where it generates a new transition on demand based on the value of a field. You can use one All (global) transition, and then you would have to create separate transitions from all of the other statuses. Or you could have an…

I never mentioned a validator - only conditions. Have you tried what I suggested? And if not, why not? 

You can't have one transition use values or post functions in another transition - each transition is independent. Did you try to implement what I suggested? What will not work for that? 

Hi @Gökhan Sarıkaya - Can you provide an exact example of the process and who should approve when? And also it would be nice to have a screenshot of your workflow. 

So the field doesn't show to map against? Is that the issue? 

You are welcome - and a nice day to you, also. :-)

Hi Neelam - Welcome to the Atlassian Community! Check the history of the field to see who is shown as updating the assignee field. I suspect you are setting that in a post function of the workflow or through another automation rule. So, when you execute it, immediately check the audit log for the all automation rules…

Hi Rituraj - Welcome to the Atlassian Community! Let's clear up one thing first. Transitions do not call transitions. Issues move from one status to another status using a transition. So you could say one status calls another one if you want, but that's not a good way of saying. So you simply have two transitions from…

You need to click on the transition from Wartend (Waiting?) to Closed. Then see if there is a post function that sets the Resolution field to Done or something like that. If not add one. 

Hi Jyotsna, You will probably need an add-on like JMWE or ScriptRunner to be able to do custom validator/conditions. With that, you should be able to do that. Create a custom field such as radio buttons or single pick list with values of No and Yes. You can call it something like Are you sure? Add the description you would…

The workflows that you see when you go through the first part is for Company-managed projects only. This allows you to create workflows that are shared across Company-managed projects. Workflows created within Team-managed projects are only available for that single project. So if this is a Team-managed project, you have…

So you need to check the workflow for the transition from Waiting > Closed and add a post function to set the Resolution field value. 

Hi Raha, Are you talking about open issues for Atlassian to fix? 

Hi Kim, No, that's not currently possible. You might could create a custom field but it would not be able to validate that the issue key entered is the correct one. But guide the users to enter the issue key only, for example, ABC-123. Then you would use automation to update the parent field with this value. That's all…

Hi Waseem, The All Open Tickets is probably based on the Resolution field (filter says unresolved). You need to make sure you are setting the Resolution field with a post function on the transition to Closed. (Assuming you are using a Company-managed project). 

Hi Tony, What type of project are you using? Jira Software? Jira Work Management? Team-managed? Company-managed? Are you only trying to move them on the board for the Sub-tasks? Or did you also go directly into the issue and try to update the status there? Are you using the same workflow for the sub-task as you are for the…

Hi Christopher, You can simply create multiple transitions and add a condition for the separate issue types. Then in the one where it is required, add a Field Required validator. 

Hi @dkwan Another option is to create a second board based on a Jira Software board but using a filter for you JWM project. You can see how to do that in this article: https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018