User Stories / Epics

[Max]

Dear all,

I am new to Jira and have a small private project running.
Unfortunately, I only found jira in the middle of our project and then added all the sprints and user stories in jira.
I didn't pay attention to when I complete user stories in Jira. When I switched from Excel to Jira, I took over the user stories and simply set the user stories to completed.
This does not look good in the burn down diagram, as it looks like all tasks were completed in one day.

1. Can I complete user stories retroactively and date them to a desired date?
I would like to create a traceable burn durn diagram.

2. I have already closed a sprint by completing all user stories in one day.
The burn down diagram is therefore not correct.
Unfortunately, when I reopen the sprint, all the user stories are no longer available.
-->Are these user stories now gone or can I restore them?

I would be pleased to receive support...

Best regards,
Max

[Max]

Hi @Trudy Claspill ,

1. it worked, see screenshot 1. Many thanks!!

2. But now I wanted to change the date again for the same user story via Excel. But that doesn't work. See screenshot 2.
Is it only possible to change the date once via Excel?

3. I have already created a burndown diagram for the project (screenshot 3). But I don't understand why the user story that I finished earlier via Excel is not moved to 16 May and is therefore displayed earlier.
What is the reason for this?

4. The point no longer has anything to do with the upper ones, but when I want to end a sprint, this message always appears (screenshot 4). 
But I have completed the issues (see screenshot no. 5). This also looks a bit silly in the dashboard, see screenshot 6

Can you help me here too?

Best regards,
Max

[Trudy Claspill]

2. But now I wanted to change the date again for the same user story via Excel. But that doesn't work. See screenshot 2.
Is it only possible to change the date once via Excel?

Are you using the same CSV file, with a new date value, and trying to import it again using the same field mapping?

3. I have already created a burndown diagram for the project (screenshot 3). But I don't understand why the user story that I finished earlier via Excel is not moved to 16 May and is therefore displayed earlier.
What is the reason for this?

I had not fully tested this myself and have now done a bit more testing.

The burndown is based on when the issue is moved to a status mapped to the column farthest to the right on your board. It is not based on the Resolved date. So changing the Resolved date in the issue does not change the burndown chart. I think the only way to change the burndown chart would be to change the history records for the issue, and I don't know of a way to do that.

4. The point no longer has anything to do with the upper ones, but when I want to end a sprint, this message always appears (screenshot 4). 
But I have completed the issues (see screenshot no. 5). This also looks a bit silly in the dashboard, see screenshot 6

In a sprint an issue is considered "complete" only if it appears in the column farthest to the right on the scrum board. Is the Done status mapped to the column farthest to the right on the scrum board? If it is not, then the issue will not be considered "complete".

[Max]

Hello @Trudy Claspill ,

Many thanks for your tips.

1. I have managed to import the Excel.
Unfortunately, the existing user stories are not updated, but all user stories are simply loaded into the backlog again by the Excel. Is it not possible to simply update the existing user stories?

2. The user stories that were then additionally uploaded to the backlog by Excel do not contain the desired date that I specified in Excel.
In the line ‘Resolved’, I had selected ‘resolved’ when I imported the Excel.
The rest of the lines I left on ‘Don't map this field’.

[Trudy Claspill]

Hello @Max 

The Resolved date is set automatically when you set the Resolution field for an issue. That normally occurs when the issue Status is changed to one of the done/complete/closed statuses.

It is not possible to update that date through entry in a field in the UI, but you can update the value by using the CSV Import function. You would use the View All Issues screen to select the issues you want to update and export the data to a CSV format. You need to have in that exported data the Issue Key, Issue Type, Issue Summary, Resolution, and Resolved fields. In the CSV you then modify the Resolved date/time to the date you want. Then a Jira Admin can use the Import External System > CSV  option to import that modified CSV file, mapping the fields appropriately, and the Resolved date/time will be updated.

For point #2, if that is still an issue, please show us the Sprint Report showing all the issues in the sprint, and then show use the scrum board for that sprint after you reopen it.

[Max]

Hello Trudy, 

thank you very much for your answer!
My concern is that the whole project will break if I re-import an Excel.
I'm using the next gen version of Jira and somehow I can't make a proper backup.


The second is that I cannot set a reasonable filter via the search, so that the required values are output in the Excel you meant (Issue Key, Issue Type, Issue Summary, Resolution, and Resolved fields).
The search mask does not allow proper search entries.

I have attached a screenshot for both points.

I would be pleased to receive a reply.

Best regards,
Max

[Trudy Claspill]

Hello @Max 

You mention that you are new to Jira, so I recommend that you take some time to review the documentation on how to search for issues.

https://support.atlassian.com/jira-software-cloud/docs/search-for-issues-in-jira/

And consider taking the free training on the same topic from Atlassian University.

https://university.atlassian.com/student/path/1687678-finding-information-with-search-and-filters-in-jira

To find issues in sprints you can use the sprint field.

https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Sprint

To set up the fields you want to export:

1. Click on the List View button.

2. Then click on the Configure Columns button.

3. Then search for and select the columns you want to display.

After executing the search and selecting the columns, you can then click the Export Issues button and select

If you are concerned about doing something wrong, try updating just one or two issues first to make sure you have made the correct updates in the CSV file.  You could also set up a second project and add some test data to it, and work first on updating the test data to make sure you have it figured out correctly.

If you want to make a backup before making any changes then you need to use the Backup for Cloud option.

[Trudy Claspill]

You have to map the five fields in order for existing issues to be updated 

Issue Key

Summary

Resolution

Resolved

Issue type