You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When an issue is planned for a release/version; can the release date be considered as due date/target date in portfolio?
Or is there an easy method to sync the due date with release date?
Thanks in advance, and regards,
Hey @Hans Meijer ,
There is some light coupling between release date and issue end date - although admittedly not in the way that you're describing. If an issue is assigned to a release and its end date is set after the release date then the release will be shown as off track. Unfortunately the issue in question is not displayed differently and the end date is not applied.
We have actually done some experimentation with inferring issue dates from release dates (as is also possible with sprints) but are not yet committed to making that change at the present time - however, this does sound like it would do what you want, except that the dates would only be visible in the plan and not persisted to the issues (which I'm guessing you wouldn't want).
I think that the suggestion that @Fazila Ashraf is an interesting one and it might be possible with the automation features that also come with Jira Premium (if you're using our Cloud platform - you've not tagged this question with Cloud or Server so I can't tell!)
Hi @Hans Meijer ,
Unfortunately there is no specific issue at the moment because we're not actually sure if we're going to take those prototypes any further or if they're going to become part of something else, therefore we've not raised an issue that could be tracked yet.
A year an a half after the original post I note that scheduling by Release is possible in Cloud:
Is there any chance that this will become available in Data Center? It seems that currently only scheduling by Sprint is possible.
We are using Roadmaps to track delivery of business objectives, which are comprised of Epics, which in turn will be considered delivered only when the last Story has been Released. Sprint dates are not helpful here, as on some platforms they can perhaps conclude several weeks prior to their release.
Furthermore, we can't base our Roadmaps on boards as the list of projects contributing to an Epic is potentially unknown; instead our Roadmaps are filtered on children of Epics, whatever their project maybe. As we don't include boards, even Sprint scheduling is unavailable to us.
Roadmaps already imports the Releases of the Stories and, separately, the Release dates. It seems crazy not to join these up.
@Hans Meijer , i was in the same situation and what i did was - using the scriptrunner's scriptlistener, i scripted that when ever a ticket in the project is edited, copy the 'custom date' field to 'target end date'.