Automation Failure

[Jeremy Barton]

Hey Jira Crowd,

I'm new to Jira and am trying to create an automation for which queue a new tasks falls into based upon which team member is creating it.

I am probably doing this the hard way, but I thought it would still work.  I created a rule:

-  Task Creation -> Transition -> Reporter -> Name

It works for about 10 minutes after I create the rules, and then Jira crashes and I get the attached picture with the failure warning.

Any ideas how I can keep it from crashing?

Thanks!

[John Funk · Accepted solution]

Hi Jeremy - According to your error, the Reporter field is not on the transition screen. Try adding that field to the Transition screen or whatever screen you are using when you cause the trigger to fire. 

[Jeremy Barton]

Thanks John!

Man, I have to admit, I'm not sure how to execute that.

Reporter is a default field when someone creates a Task, so by default it is included on that screen, correct?

Do I need to add it to the boards where the task lands after creation?

[Mark Chaimungkalanont]

If you're not seeing a screen when you're transitioning your issues manually, your transition probably doesn't have a screen associated with it.

A simpler way would be to remove the "Reporter" field from your Automation rule's transition action.  (from the screenshot, where you're assigning it to Blair). Then add a new action that assigns the issue to Blair, or whoever you need. You'll have two actions but it'll mean you don't need to change your workflow

[John Funk]

Can you view the Create and Edit screen for the project to verify that the Reporter field is on those screens?

[Jeremy Barton]

Hey guys,

Thanks for the help.

@Mark Chaimungkalanont ...My goal is that when Blair creates a task, that it automatically goes to a specific location.  We have 2 teams, and I would like their created tasks to hit their respective backlogs.  Is there a better way to do this than by using the "Reporter" field?

@John Funk , I attached the Create Screen below...when you say "Edit Screen", do you mean "Edit" within the task?

To both of you, and perhaps more fundamentally, what is the "Transition Screen"?  Is it the initial board that a task falls to in the workflow?

Thank you,

[John Funk]

Within a screen scheme, there can be a Create Screen, and Edit screen and a View screen. So, got to Settings > Screens and find the Screen Scheme being used by the project. 

A transition screen can be attached to a transition in the workflow so that when a user changes statuses, it fires a transition and if there is a transition screen attached, it will be presented to the user. 

[Jeremy Barton]

Well, I think I found an automation that works!

I set a condition equal to the reporter.  That seems to not fail after 2 minutes, for now.

[Jack Brickey]

Hi Jeremy, before we dive into the Automation I would like to explore if it is even needed. Can you explain exactly what you are trying to achieve? Are you wanting to auto assign issues and if so based upon what criteria. I wonder if it might be possible to simply define the queues based upon the criteria.

finally, can you open one of your rules and capture it here for me to examine. Also, check the log to see what error it is providing.

[Jeremy Barton]

Sure!  Thanks!

We have 3 teams...Mgmt, Architecture, and Customer Success.  It is a single project broken out into 3 boards.

I would like when Mgmt creates tasks for it to hit a certain Kanban column on their board, and when team members of each team create tasks, for it to hit their respective backlogs (as opposed to defaulting to the mgmt board)