Multiple staggered updates on a weekly release schedule, live bug tracking issues.

[Vicki Morris]

Hi,

We have only really just started using JIRA for the project I am working on. Traditionally we use waterfall method for development.

We have a multiple update staggered weekly release system all for one project, which we have set up a custom workflow for. Individual parts of weekly releases can range in development time, from a few days to several months, meaning we try to have strict process and timecosting to hit key dates, we can also have completely separate updates going out at the same time.

In order to manage our individual weekly releases, we have decided to use fix versions within the larger overarching project, which covers one of our products.

One of the things we are having difficulty with is in live bug tracking once a version has been released [we are only trialing this on one thing at the moment and this is a stumbling block].

• Sometimes we have to hit the release, and update even if we know not all issues are fixed within the time frame, however we can't release a fix version if there are outstanding issues.
• We still want to be able to associate these issues with that specific part of the release, as they are always separate updates that different developers work on and we need to monitor this.

Does anyone know the best way to do this?

I am the first to admit that I am still not completely clued up on this system so you will have to forgive my ignorance.

Thanks in advance

Vicki

[Renjith Pillai]

Vicki: Jira does not prevent from releasing a version even if there are issues which are unresolved. You can still go ahead and release those versions without moving the issues to the next version.