Which screen does Automation pull from?

[Lindsay Donaldson]

I have been tinkering with an old system and made some changes to screens including adding new fields. It is for allowing HR to create an "issue" with some basics of a new starter, which then is passed to the line manager to complete with other information (such as what system access, security pass access, etc).

We have automation set up to create subtasks based on the line managers' entries - this screen is a series of questions (custom fields) set out over a few tabs. The automation can recognize which subtasks to create (so if no information is entered on the relevant tab then the subtask is not created). 

However, the automation task doesn't seem to pull the information from the line manager's screen. If I ask Jira to find the field (I have tested by entering information into a test issue) it says that there is no information and hence is hidden. There are also a couple of defaulted fields (9/10 the field will be yes), but if no is selected on the line manager screen then the subtask still enters this as a yes. 

Is there any way I can find out which screen the information is pulled from? The task is set to "copy from issue" as with another task which works fine. Do I have to have the relevancy fields available on another screen (such as on the initially created issue)?

I'm rather confused at the moment and this problem means that a lot of information that the line manager is entering is getting lost (I can't even find the information on the line manager screen as this is only a step-through screen. If anyone can point me in the right direction or to a tutorial/guide I would be most grateful. 

----

This is some of one of the automation tasks that isn't working with the subsequent output. Please note that information was entered into each box or checkboxes/radio buttons were also selected. (As with the Horizon/Email account "no" was selected yet "yes" has been returned).

[Sebastian Kurrek]

Hello Lindsay

"but if no is selected on the line manager screen then the subtask still enters this as a yes."

I saw some similar behavior. I added information to an issue but the automation works with the old information. 

You created a custom event "Line manager Star Form Complete" which is user within a postfunction?

Could you make sure that Jira updates the index of the updated issue bevor you trigger your automation rule?