-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
7
-
At the moment portfolio doesn't support "version picker" custom fields.
We use currently use "Fix Version/s" for complete tasks and a custom field called "Target Version" for planning purposes. Unfortunately setting the "Releases" field updates the wrong field.
Two options
- Add support for "Version Picker" custom fields
- Allow "Releases" to update custom fields
- relates to
-
- Gathering Interest
- links to
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-24961] Add support for version picker custom fields
Please consider this improvement for escalation, our team would like to set a Target Version field but is unable to because it doesn't assign Target Versions to releases, Fix Version does not cover our specific needs.
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
Same need with our custom field "Target Version" for planning purposes.
Having a clear distinction and the ability to track plan versus realized would definitely help to adopt "Advanced Roadmaps"
+ 1. This is a real life example to see difference between what's proposed and what's targeted. Lack of this is hidering us to use advanced roadmap effectively for planning exercise.
Hello there,
This issue is preventing many people in our organization from using Advanced Roadmap. I sincerely hope it's fixed soon.
We have the same needs, even if just allowing Target Version to show up in Portfolio tool would be helpful for us. Our use case for this is that it allow us to see the Target Version of the item and then cross check with the scheduled end time so we can see the scheduling risk. The ideal situation would be able to modify the Target Version from the tool directly.
We have the same requirement, just the name of the custom field is different.
We are running according SAFe and we would like to mark the target "program increment" (set of several sprints) on the Feature level. We use the hierarchy: Story-Epic-Feature-Initiative, where the "Feature" is defined as "capability which can be implemented by N teams (1 release train) within 1 program increment" ...
Hey, I have run into the same problem. I've created a custom version picker field that we use to track milestones. However, any issue with this custom version picker filled out with a release version does not appear in releases. Any help with fixing this issue would be greatly appreciated, using fix version or affects version does not cover our needs.