How do I change the start date of a version?

I'm using Greenhopper 6.2. How does one modify the start date of a version after the version has been created?

2 answers

1 accepted

Hi Peter,

If you mean the Versions in the new panel, you can click on the current start date to edit it in GreenHopper 6.2. If it doesn't have a start date, it should say "None" - just click on that and it should allow you to edit it.

Here are more details:

Thanks, JoAnne.

I'm assuming you mean sprint? See instructions here. If that's not what you mean, can you clarify? :)

No, I mean version (aka "release" at my company or fixVersion in JIRA field terminology). Many sprints are in one version. The new Version Report is a nice release burnup on steroids, but I need to know how to change the start date used in the chart.

Hey Peter, versions don't have start dates, they have Release Dates. Sprints have start and end dates. If you're using the new agile/scrum boards, those are based off of sprints, not versions. You can still use the Classic boards, which are based off versions, but again, those do not have start dates. There are some dashboard gadgets which work with Classic boards, and those have start that what you mean

Versions do have start dates. Show the Versions panel while in Planning mode on a board. Click the "+" to create a new version and you will see that you can enter a start date.

The question I have is how to modify that start date after the version has been created.

My apologies, Peter - all this criss-cross of functionality between classic and new, sprints and versions, is totally confusing sometimes. Found your answer:

In Classic Planning Board, with version selected that you wish to edit, on the right side make sure the "expand all" button has been activated. You should see the version in the column with all its fields; there is a pencil next to each field, including Start Date, you can edit from there. You need to be an adminstrator (documentation from Atlassian doesn't state if they mean JIRA admin or admin permission to project, scroll down to #10 in that page to see what I mean) in order to edit the field. Sorry for all the confusion!

Sorry, can't edit my comment - this is the url I meant so you can scroll to #10 (the one above goes to bottom of page).

It's been so long since I've used the Classic board that I forgot about that angle. I hope there's a straightforward, transparent method in the pipeline.

Agreed - the terminology and functionality is getting so confusing since GreenHopper is attempting to run two different methodologies. I'm looking forward to the removal of "classic" and streamlining of the new boards. Sorry again for my confusion, and I'm glad I was finally able to find you the correct answer :)

It sure sounds like Peter could be referring to the new "Versions" that you can now see in Plan mode on a Scrum board on the new Boards (not classic Planning Board). The Versions tab shows up right next to the Epics tab.

Peter, is this what you are referring to?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

625 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you