Problem Definition
In general: accessing the fields is only through advanced JSON
There are a number of fields that are attached to a list set through a gantt chart like UI i.e. Target start, Target due date etc. However, the above fields aren't actually attached to the issue, so probably require integration with Portfolio for Jira's API
Expected Behaviour
It should be possible to select and edit Portfolio fields (like Team, Target Start, Target End ) in Automation for JIRA.
Failures caused by this lack of support to Advanced Roadmaps' fields.
While it is possible to use the Edit Issue action's advanced section (i.e. the one available by clicking on the More options button), due to the lack of support to the Target Start and Target End fields, if you attempt to use any date functions (such as plusMonths, minusMinutes) the automation rule will fail due to a parsing failure.
Original CB ticket for reference:
- links to
[JIRAAUTOSERVER-159] Provide Support for Portfolio/Advanced Roadmaps for Jira fields (Team, Target Start, Target End)
Really important field for my team as we use it to align with program management and we can't trigger easily that when the task goes to in progress we can update the target start date automatically if the field wasn't set previously and then estimate the target end date based on the hours entered by the assignee. Not having the date function hinders keeping things updated automatically in the portfolio view since the portfolio doesn't show the gantt chart based on due date.
I'd love to have this feature. I'm trying to update the Target end date of one story based on the Target end date of another story. I thought the guide noted in comments here would help, but I still get parsing errors. Frustrating.
if you are looking for a way to copy the Team field to another custom field, you might want to check this KB article which provides a solution involving the paid add-on ScriptRunner:
https://confluence.atlassian.com/jirakb/how-to-copy-advance-roadmaps-team-field-value-to-another-custom-field-1115132922.html
As Bill has pointed out, the Target Start and Target End can be edited with the "Additional fields" JSON style section.
We've put together a how to guide here which covers the basics - How to update a story's target start and end dates based on the sprint dates using Jira Automation
I desperately need this functionality! https://community.atlassian.com/t5/Automation-questions/How-can-I-set-Target-Start-to-present-day/qaq-p/1850821#U1851094
My most significant use-cases are frustrated by Automation not natively "seeing" the (Plan/Roadmap) Team field.
I elaborated on some of these use-cases in my 16-Mar-2021 comment on the thread I linked above.
Hi! Is the issue that the fields Target Start and Target End can only be updated with JSON advanced edit rather than from the field drop-down list?
I tried capturing and updating the fields (using created variables as intermediaries to increment the days with plusDays() ) and it seems to work.
Thanks,
Bill
See also Atlassian Community discussion here:
https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-get-an-user-s-Team-through-the-Rest-api/qaq-p/1233621
Hello! I really need this feature in next case. I have a JIRA plan, created and based on JQL for some module. This JQL contains up to 60 tasks (see screenshot attached below). There are fields "Target Start" and "Target End" in this JIRA plan. So, it will be grateful to have possibility in JIRA-automation:
Now I have to set these fields manually.
I would be grateful if this case will be taken into account in future development milestones.