Loading...

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Details

Type: Suggestion
Resolution: Obsolete
Fix Version/s: 2.0.0
Component/s: None
Labels:
None

Feedback Policy:

JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

Description

NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

When linking a JIRA issue to an existing Portfolio issue, an initial synchronisation between the two items should happen in the following way:

Empty values for title/description/estimates in Portfolio should be filled with available values in the respective fields of the linked JIRA issue and vice versa. In case there is values in both, the JIRA issue and the Portfolio work item, either no synchronisation should happen or the user should be able to configure in which direction the sync should happen.

Attachments

Issue Links

duplicates

JPOSERVER-1350 Linking JP Backlog item to estimated JIRA story doesn't take estimate in JP

Closed

relates to

JPOSERVER-42 JIRA Portfolio integration with JIRA Agile

Closed

JSWCLOUD-19642 Create and link existing issues should provide an immediate sync between JIRA and Portfolio

Closed

mentioned in: Page Loading...

Activity

People

Assignee:: Unassigned

Reporter:: Albert Kavelar

Archiver:: Aakrity Tibrewal

Dates

Created:: 14/Aug/2015 12:18 AM

Updated:: 19/Sep/2019 6:00 AM

Resolved:: 07/Jun/2016 4:13 AM

Archived:: 12/Oct/2023 2:33 AM