nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Resolution date is not set

Ad Smeets

I have two projects in JIRA which use the 'Automation for JIRA' plugin so set the resolution to a desired value based on a specific transition.

My assumption would be that the field 'resolution date' would be filled automatically in this action. In one of the projects this is the case. In the other project the fields is empty. A difference I can not understand. The resolution is set succesfully to the proper value.

Is both cases no screen is required to do the transition to the desired state, but that should matter.

Does anyone have any suggestions how I can find the cause to this issue and even better a solution?

Accepted answers

Alexey Matveev

Hello,

I would have a look at the workflow post functions for the issues, where the resolution is not set. There could be a post function from a plugin.

If you have plugins installed in your Jira, it could be any of these plugins doing the thing. You can copy your production instance to a staging instance and switch to safe mode. Then have a look how the resolution date behaves. If everything is fine, then it should be one of the plugins. You can enable plugins one by one and find the plugin.

All comments

Alexey Matveev

Hello,

I would have a look at the workflow post functions for the issues, where the resolution is not set. There could be a post function from a plugin.

Andrew I

Hi @Ad Smeets!
I have the same problem. Could you share, how did you solve it?
Which plugins or post functions prevented the resolution date?

Ad Smeets

Hi Andrew,

Tried a lot of things with Automation for JIRA but none of them worked flawless. I even got a confirmation that this does not work as I expected.

So in the end I resolved it by using the post functions in JIRA. They work fine and all the time.

Andrew I

I have resolved this problem by adding Resolution to Transition issue

image (7).png

Instead of this:
image (8).png

George Mihailoff

@Ad Smeets without details it is hard to say. Most likely the workflow in the other project is more complex, maybe the status category of the end status is not correct, maybe something else.

Rinaldi James Michael

I have the same issue. I had created an automation to update the resolution to done whenever an issue was moved to the Done status.

But the resolutiondate was not set by the Automation plug in like it would have by a workflow transition's post function.

Is there any additional module that can be added to the automation rule instead of adding a post function to the workflow? Or can this feature be addressed to the Automation plug in team?

Rinaldi James Michael

I think the issue is fixed now for Jira Cloud at least without adding a post function to the workflow's transition. Not sure why it didn't work earlier. Also not sure if the issue still persists for Jira Software and Data Center.

Adriano Bittar

I am having the same problem.

I created the automation function and now is updating the resolution field, however the resolution date (resolved) is still blank.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

automation