Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Linked issue is being removed when the issue is moved to another project if I have a epic attached Edited

I have two projects. One is a company-managed project and the other one is a team-managed project.

Short question:

There's any way to keep the links between stories when we move a story, that has a Epic to it, to a new project?

How to simulate:

1. I have the following in the company-managed project:

EpicA -> StoryA

2. Then I clone the StoryA, which will create the ClonedA story. Now I have the following stories and links:

EpicA -> StoryA(link - is cloned by ClonedA)
EpicA -> ClonedA(link - clones StoryA)

3. Now I move ClonedA to the team-managed project and the following message is shown:

CMP-18 will lose the relationship with its parent epic.

You're moving this issue away from its parent epic. To avoid losing the relationship between this issue and its parent, move the epic issue as well.

Note: The epic relationship won't be lost when moving between classic projects.

ps. I do not want to move the epic.

In the following screens, it's not informed anywhere that I would be losing the link clones StoryA when I move it to the other project.

4. The ClonedA and StoryA loses its linked issues.

No mention on anything like that here: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/#keepInMind

Important: The removal of the links does not happen if there's no Epic in story A.
Important2: This only happens on moves between company-managed and team-managed projects.

1 answer

The links between Epics and child issue are managed differently between Company Managed projects and Team Managed projects.

In a Company Managed project, the child issue is linked to the Epic by storing the Epic issue ID in the Epic Link field.

In a Team Managed project, the child issue is linked to the Epic by storing the Epic issue ID in the Parent field.

Additionally, Team Managed projects were designed to be "stand-alone" entities - they have their own per-project customizations for fields and workflows, for example, and these customizations are not available to share directly with other projects. The projects were not designed to support cross-project linking of Epics and child issues.

You will not be able to maintain links between Epics and child issues when those exist in separate projects.

 

I have not looked much at the use of generic links between issues in Team Managed projects, nor the impact to those links when moving issues between Team Managed and Company Managed projects.

Are you saying the clones link is removed also, but only if the issue you are moving also has an Epic link? If the issue being moved does not have an Epic link, then the clones link is retained when the issue is moved?

Are you saying the clones link is removed also, but only if the issue you are moving also has an Epic link? If the issue being moved does not have an Epic link, then the clones link is retained when the issue is moved?

Yes, the clones link is only removed when there's an EPIC, if not, the clones is retained.

Jira does not warn me about this behavior. I found it odd because if I do not have an EPIC to the story, the clones link is not removed.

I recommend that you open a support case directly with Atlassian concerning this behavior. It may be a bug and they may or may not already have it in their backlog.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

314 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you