If I created an Issue let's say today December 3rd 2018 and then the issue got fixed on the second day December 4th 2018 but I forgot to close it on this day and remembered at later times to close the issue. How can I close it entering the original date 4th December 2018 (retrospectively) ?
Not sure if that's possible, because it takes dates automatically.
My first question would be: (why) is it really that important that a ticket is closed on day later? I can't help myself from getting the feeling some micromanagement is happening here...
However, there could be a good reason, so here are two easy ways you can do this:
1) Custom field with a date format, where you select your close date.
2) Close the ticket and if you are too late, add a comment and flag the ticket.
Based on your question, I assume the date is quite important and some kind of reports are based on it. That is why I would forget step one with the custom field, because you will not only have an extra field to take care of, not helping you in retrieving data.
Only add an extra field, if you are planning on using this field more often. Remember that the need to immediately close a ticket won't be needed, because you can change the close date at any time with the custom field.
Advice: Don't make things too difficult and too tight
Just close the ticket, add a comment and flag it is the most simple approach, and if applicable, manually update the report, or add a comment.
Can we update the issue with the new date using CSV?
I'm kind of in the same situation. They forgot to close a ticket on "Sprint 2" and now they are in Sprint 4. So we want to close the ticket on Sprint 2 , to get the burndown correctly.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since Close Date or Resolution Date both are controlled automatically by JIRA and you can not change them . So you can create a new custom field for tracking the original close date and that field must be entered manually by a user.
Regards
Prakhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.