how to update start,end,completed date of closed jira sprint

[hpapoushado]

 seems i must reopen , change and once i complete it set the completed day to today, I want the completed date to be the end date, 

there is an explanation how to manipulate the DB to do so , but in cloud I understand I cant do this manipulation.

i tried Jira python , but it didn't update when sprint was closed , I hadto reopen it , run the script, it changes start and end , but again completed is today . 

[Walter Buggenhout]

Hi @hpapoushado,

These sprint start and end dates are system dates. They are not meant to be manipulated in other ways then by executing the actions that set them, being starting and completing the sprint in Jira. 

Hope this clarifies! 

[hpapoushado]

i know 

but we ran into a problem , and we need to edit it :-(

 if there is a way to update start and end date , why not completed dates ? 

[Walter Buggenhout]

Hi @hpapoushado,

don't bother. In an organization starting to do agile (and basically doing anything), making mistakes is indeed part of the process. Don't try to hide them, though - embrace them and use them to improve. 

Run a retrospective and document what you see and how you are going to change that. The goal of a scrum team is to deliver working software, not follow a rigid process. 

[andy.johnston]

I'm not sure this is 100% correct.  The sprint start and end dates are manually able to be set, and they are able to be set in the past once the sprint is active. The difference is the Sprint Completion date (which is the only able to be set when the sprint is completed).  And apps like Bigpicture use that date... then say all my old sprints are overlapping!?!

This is important for me as I"m trying to migrate old backlogs from ADO.  Mapping them to the Jira sprints, and then closing all the old ones once the import is complete.

Basically - it stuffs importing.  So I wanted to be able to go into the API and update the old sprint completion dates so they don't overlap (and match up with the sprint end dates which are correct.....but even with 500 upvotes Atlassian closed out the open request with a "no go" sort of message. https://jira.atlassian.com/browse/JSWCLOUD-16331

I'm just going to migrate the most recent sprint, and push them back to ADO for history.  What a crap option when I'm so close with one date change.... sigh.

[Marc - Devoteam]

Hi @hpapoushado 

As @Walter Buggenhout mentions this is bad practice.

People in your organisation need to look at their process, not due to process manipulate information in the system.

As you are running on Cloud their is no DB manipulation possible, as you don't have DB access.

[hpapoushado]

its strange, if its available in DB manipulation, why not also in API ? 

i do agree its bad practice , its an organization that steps into agile and jira and still people do mistakes , I want to fix it. 

[Marc - Devoteam]

Hi @hpapoushado 

DB manipulation only works on self hosted DC, not on Cloud.

In Cloud there is no DB access, also not via API.