-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
2
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Currently, Portfolio does not offer separate fields to represent an Agile Epic's name and summary, both fields are represented by the Epic title in Portfolio.
Current behaviour:
When applying updates to linked Projects and and enabling summary syncing, the title configured in Portfolio is set to summary and name of the linked Agile Epic. The same goes for automatic two-way synchronization of summaries between JIRA and Portfolio. Changing either Epic name or summary in JIRA will propagate the new value to Portfolio. Changing the title in Portfolio will set Epic name and summary in JIRA.
Desired behaviour:
Portofolio provides a separate field for the Epic name (e.g., in the details page of a backlog item) and maps the title to the Epic summary. This way, the two fields could be synced independently and a change to the Epic title in Portfolio would then not unexpectedly overwrite the Epic name in JIRA.
- relates to
-
JPOSERVER-330 JIRA Portfolio overwrites Epic Name when synchronizing with JIRA Agile
-
- Closed
-
-
- Gathering Interest
-
- Gathering Interest
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25208] Allow to manage Epic name and summary independently in Portfolio
Brad's suggestion that Portfolio should only read/write from ONE field: Epic Name makes good sense to me
Blair Streit
added a comment - The root cause is that Epic is a "special snowflake" in JIRA. Until that is fixed, I think a lot of the weirdness in dealing with Epics will hang around. Notice that we don't have the same issues with other levels of the hierarchy....
Blair Streit
added a comment - The root cause is that Epic is a "special snowflake" in JIRA. Until that is fixed, I think a lot of the weirdness in dealing with Epics will hang around. Notice that we don't have the same issues with other levels of the hierarchy....
https://jira.atlassian.com/browse/JSWSERVER-8851 +1 I also think that in the lozenge the JIRA Epic name (short name) should be used and synchronized (or just used from JIRA Agile) both ways.
+1 to all of the above comments. This is a big deal when information is sync'd both ways...very frustrating.
Also, I agree with Brad that Portfolio should only read/write from ONE field: Epic Name.
This is a serious BUG, not even a suggestion. I just inadvertently renamed a few hundred Epics because of this bug. Not fun. PLEASE FIX THIS.
Marianne Phinney
added a comment - This is really disturbing to our POs, who use short epic names that will display in the lozenges on the backlog. I don't mind seeing the summary title in Portfolio, but it shouldn't change the Epic name in the Jira ticket. This makes synchronization totally worthless for us.
Marianne Phinney
added a comment - This is really disturbing to our POs, who use short epic names that will display in the lozenges on the backlog. I don't mind seeing the summary title in Portfolio, but it shouldn't change the Epic name in the Jira ticket. This makes synchronization totally worthless for us. 
brad sherman
added a comment - If not the ability to manage these independently in Portfolio, at least make it so Portfolio only reads from and writes back to one of them in Jira.
Reading from one of them in Jira, and then writing back to both of them is, IMHO, non-sensical
Regards,
Brad
brad sherman
added a comment - If not the ability to manage these independently in Portfolio, at least make it so Portfolio only reads from and writes back to one of them in Jira.
Reading from one of them in Jira, and then writing back to both of them is, IMHO, non-sensical
Regards,
Brad
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