So this project was recently created on Jira, where resolution field was missing. Since we are using Company Managed Jira, I requested to add resolution field to all the issue types.
Once the resolution field was added, what I see is when new issues are created, by default issues are with resolution set to unresolved, due to which there is no strike-through over Jira issues when I see in Backlog, but suppose I want to edit the issue, let's say add few more details like adding Sprint, Epic Link, Updating Story Points, then automatically in the edit pop up, resolution shows complete as status, which we have to manually set it back to incomplete. Also due to this, there is strike-through over the issues.
What can I do to resolve this ? Only issues with resolution as unresolved are not strike-through stories, and there is no option to select unresolved, while editing the issue.
Hi @Chetan Krishna , welcome to the community!
Let me see if I understand your concern:
Could you please clarify when you are noticing the resolution field is being updated to "Completed"?
My hunch is that part of your workflow is updating the Resolution value to be Complete. However, without more information I cannot be certain.
If your workflow is configured incorrectly, you will likely need your IT team to help reconfigure it.
While we're on the topic, are you able to share a screenshot of your issue's workflow diagram? That will help understand at what point you want the Resolution field to be populated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It happens when I edit an issue, regardless of where it is in the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Chetan Krishna That is very strange.
Could you please test something for me? Please create a new issue, and do not edit it. After 5 minutes, please refresh the screen. Does the resolution stay "Unresolved" or does it go to "Resolved"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah! @Chetan Krishna that sounds like your Admins have configured the "Resolution" field to have a default value.
I would recommend reaching out to your admins and asking them to first check to see if the Resolutions field has a default value, and if it does, to clear it.
Here's a screenshot to show them:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Robert DaSilva . I have raised a request to Jira Admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.