resolution screen unfilled fields

[Ivan Andrieiev]

after closing the task with the resolution screen, the unfilled fields disappear, which prevents the execution of the automation rules.
Is it possible to somehow keep them active?

[Trudy Claspill · Accepted solution]

Hello @Ivan Andrieiev 

Can you please provide more information? What do you mean the unfilled fields disappear? Can you provide a screen image of the Resolution screen, and another screen image that shows the fields have disappeared?

Can you show us the Automation Rules that are not working? And also show the Audit Logs for the rules?

Are the rules not being triggered? Or are they being triggered but not then producing the result you expect?

[Ivan Andrieiev]

It is situation for @"Canseled" status.

I suppose, you can't edit fields after resolution and it is a reason for mistake.

[Ivan Andrieiev]

@Trudy Claspill  Hi

This is a very difficult puzzle
I have a rule to set the actual end when the task is transferred to the "Closed" "Solved" status, when closing the task and choosing a resolution, the unfilled fields disappear (the actual end), but when the "Cancelled" status is selected, the field is automatically filled.

[Ivan Andrieiev]

[Trudy Claspill]

Does this rule apply to a single project or multiple projects?

Is the project containing the issues a Team Managed project or a Company Managed project?

With a Company Managed project it is possible to set Workflow Properties so that an issue may not be edited when in is in a particular status. Refer to this page:

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

Can you check the workflow for the issue type having the error to see if the property to disable editing has been set for the destination status that causes the error in the rule?

[Ivan Andrieiev]

@Trudy Claspill 

so the project is managed by the company, this rule applies to another project without a screen. but I don't seem to have a team that would block.

[Trudy Claspill]

Those are Transition Properties. 

Look at the properties associated with the Status being used that results in the error in the rule.

[Ivan Andrieiev]

it is help, thank you!!!