Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,601
Community Members
 
Community Events
176
Community Groups

Resolution date get set when a new issue is created.

Hi all,

I have an this issue with a client of mine in a Jira software project. The resolution date get set when a new issue is created in a particular Jira project. The issue began 2-3 days ago

I've checked the following:

  • Post-functions in project workflow
    • Only one and it is sending an email.
    • Workflow hadn't been touched since January.
  • Automation for jira
    • No rules is setting the resolution or the resolution date field.
  • Scriptrunner
    • No script mapped to this project
    • No scripted field for that project
  • Activitity, history and transition feed are clean.

I've found only one thread were someone had the issue in 2014 on 7.6.6 and the answer was to workaround the issue with a post-function to set the resolution field to unresolved...our field is unresolved, the issue is brand spanking new.

If you have any new pointer for me, that would be great because I don't know were to look next. I will be opening an issue with atlassian on monday.

5 answers

@ia_pmeunier 

Hello,

I had the same issue as you: issues created in a Software project triggered by a Service Management project thanks to Automation for Jira (Clone issue action) have a resolution date set while the resolution is Unresolved.

We applied the solution mentioned in [JRASERVER-70656] Default Resolution causes issues to be created with Resolution Date and empty Resolution - Create and track feature requests for Atlassian products.: clearing the default resolution in Issues/Resolution admin screen did the trick. Note that we're still using an old (7.13) version of Jira Data Center. Such a bug should be fixed in earlier versions.

Regards.

For those who don't have the fixed version available, here is my workaround:

Step 1: add a post function to clear resolution.

if you add this as number 2 (after ticket creation does not work).

ScreenHunter 3173.png

What is your jira version? It might be due to https://jira.atlassian.com/browse/JRASERVER-70656

And what about your screen schemes - is the resolution field present in view/create screens? https://community.atlassian.com/t5/Jira-questions/Why-is-quot-Resolved-quot-date-set-on-issue-creation/qaq-p/1146125

0 votes
Bryan Trummer Community Leader May 03, 2019

Just curious do all the projects share the same workflow?

Nope. I have been able to scope the issue to what we call "hybrid" projects. We combine a software with a service desk projects to add a portal feature to some software projets. The automation tool is Automation for Jira at the moment and only projects created with those rules have the resolution date set.

While being unresolved I might add.

0 votes
Tarun Sapra Community Leader May 03, 2019

Hello @ia_pmeunier 

 

Is it happening only when the issue is created? Or also when someone tries to edit the issue. Also, is the update resolution action reflected in the issue history?

This could be happening if the client has added the "Resolution" field on the edit screen of the issue. Because when he tries to edit the issue then the resolution would get automatically set. That's why it's advised to have the field only on the transition screen and not anywhere else.

I've continued my testing and it is not only in that project. It is happening in all projet. I need to change the scope of my research. I'll get back with more infos.

I'll change the focus to this:

  • Look for automation or script that are global or not restricted to a project context.
  • Any other thing that could have a global impact on the instance.
  • I will think of something else ;)

@Tarun Sapra: Yes, only when it is created. there is no resolution field in the edit screens, we use a transition screen just for that. No history at all about a change on the resolution screen.

Which is what bother me the most. If it was a modification on the resolution  field I could easily find the culprit. But the resolution date field get set while the resolution field stays unresolved. It makes it harder to scope the search...

Thanks for your answer!

Suggest an answer

Log in or Sign up to answer