In our part of the company we produce hardware and software. We often have to deal with delivery times for components or new equipement. After a bit of reading the tips of other people, I chose to make special tickets ("stories") for each component and only set target start and end dates according to the delivery times I know. Now portfolio shows them as I put them, until I add them to a "release". Then suddenly the times are changing or the whole ticket is moved etc.. I'd like to see how these delivery times impact on our releases. Is there a way that I can add these component-delivery-ticket to certain releases and having fixed start and end dates?
Hey @Josephina_Werner, at the moment there is no simple way to set fixed start and end dates for issues, as the tool is aimed for agile use cases. There are some ways you can get close, but it might not work exactly as you want:
If you estimate those issues
The way Portfolio works, an issue's length will depend on the velocity of the team. It might not be possible to exactly get the issue to start and end on a specific day. Using the "Earliest start" + "Due due date" field might help get it closer to what you want.
If you don't estimate
Check if you have Plan configuration -> Scheduling -> Unestimated item scheduling set to "Base on target dates". Then set target dates as your start and end dates.
The issue can't have a sprint, release, applied to it otherwise that will influence it's date.
Hope this helps,
Sam - Portfolio for Jira team
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events