I may have asked this before or at least stumbled onto the answer somewhere but in my haste, I didn't write it down.
I'm pretty sure there is no way to natively show the resolved date on an issue view so I was thinking I could create a custom Completed Date field and use the resolution date to populate it via post function or automation.
Does anybody of the hive mind have an alternative method other than an add-on?
My reason for this is to use it in the Advanced Planning Roadmap tool. Create the plan using Target Dates and then switch to Start and Completed custom date fields to track the real progress.
Hi Danno,
Can you be more specific where you want the Resolved date value to show? It does already show on the bottom right of an issue.
Thanks for the reply John,
Somewhere as a field that I can use mainly for the advanced roadmap planning tool.
That said I don't see it in an issue view. I am using Cloud Premium.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk, I'm guessing from what I've been reading that I need to enable work logs to get this for a given issue, is that correct? I have a hard enough time with my coworkers getting them to even transition a task to In Progress when they start. Most items go from To Do to Done.
Can you elaborate on your suggestion some more? Does it require enabling work logs? I think I saw somewhere that Epics carry an End date. Do other types of issues have this as well?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, work logs involving charging/recording time against an issue.
But the Roadmap will use the End Date for an issue, not the Resolved Date. So you should add the End Date to your issues that appear on the Roadmap, and make sure the field has a value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For me, end date is null on all tickets, even ones that are resolved/closed. I have a field for resolution time which is correct, but it does not show a date, only a stopwatch of the minutes the ticket took.
A field like resolution date or an end date that populates would be useful to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use the Resolved field for the date. But make sure you are actually setting a value for the Resolution field with a post function in your workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk That was exactly what I needed, thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk Good to see your response to my original query helped someone else.
Just to clarify, are you saying that choosing the Resolved Date in the Roadmap (I'm presuming this is in the Plans tool) will behave like the End Date? I was thinking that would require an automation to set the End Date to the Resolution Date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Danno! Well, those are two different fields that get populated differently. The Resolution date should be getting set when the Resolution field is populated. Actually its called the Resolved date and not Resolution date. If you have a field by that name, then it is probably a custom field that was created in your instance.
The End date is a field that Jira adds related to the Plans/Advanced Roadmaps. It is only populated by someone on a screen or through an automation rule, but not by the system itself. The End date is typically populated in advance as the "planned" date when the task will end. The Resolved date is populated after the fact when the work item is completed.
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.