This question is in reference to Atlassian Documentation: Publish updates to linked projects
In Porfolio, I have designated a target end date, and there is a scheduled end date automatically entered. However, when committing the issue to JIRA, the due date is not automatically populated in the new issue.
I have a similar issue... it would appear the intention of "Due Date" in JIRA is the same as "Target end" in Portfolio, but there seems to be a big disconnect between the two products.
You can "expose" (ok, just show in columns field list) "Custom fields" from JIRA, but unfortunately Due Date does not count as a custom fields so can't even be exposed, let alone proxy for the Portfolio "Target end" field.
it's very inconvenient that the jira-issue's "'due" date is in no way taken into account for the planner.
I would very much like to use this "due"-field as the "planned end" of a task. Then, combined with the "original estimate", calculate towards the beginning of the plan-period.
This way, tasks with high priority can automagically be put into the timeframe when the task is required and fit the rest around that, instead of putting all high-prio tasks at the start by default.
the only way i can do that right now, is MANUALLY adding "blocked-by"-dependencies between those tasks.
Our add-on Portfolio Toolkit allows to transfer Portfolio target dates into issues via custom fields or even to Due Date:
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot