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)
| Labels | Original: iq-a4j | New: iq-a4j ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979015 ] |
| Description |
Original:
h3. 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 h3. Expected Behaviour It should be possible to select and edit Portfolio fields (like Team, Target Start, Target End ) in Automation for JIRA. h3. 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. |
New:
h3. 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 h3. Expected Behaviour It should be possible to select and edit Portfolio fields (like Team, Target Start, Target End ) in Automation for JIRA. h3. 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. h4. h4. Original CB ticket for reference: * [https://codebarrel.atlassian.net/browse/AUT-1370] |
| UIS | New: 0 |
| Labels | New: iq-a4j |
| Remote Link | New: This issue links to "Page (Confluence)" [ 717801 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 647123 ] |
| Description |
Original:
h3. 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 h3. Expected Behaviour It should be possible to select and edit Portfolio fields (like Team, Target Start, Target End ) in Automation for JIRA. |
New:
h3. 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 h3. Expected Behaviour It should be possible to select and edit Portfolio fields (like Team, Target Start, Target End ) in Automation for JIRA. h3. 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. |
| Summary | Original: Provide Support for Portfolio/Advanced Roadmaps for Jira fields | New: Provide Support for Portfolio/Advanced Roadmaps for Jira fields (Team, Target Start, Target End) |