The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • When moving issues between projects in JIRA, should the component assignment stay the same if the same components are available?

When moving issues between projects in JIRA, should the component assignment stay the same if the same components are available?

Jasen Sparacino
Contributor
May 14, 2014

Hope that statement is clear enough.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Mike Sorensen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 14, 2014

This is an easy experiment for you to run. Create two projects with similar component lists. Then move issues among the projects with different combinations.

If it doesn't work the way you think it should, open a bug report.

https://jira.atlassian.com/browse/JRA

Jasen Sparacino
Contributor
May 14, 2014

That is the problem. They have the excate same components. I am wondering if anyone else is having this issue.

TAGS
AUG Leaders

Atlassian Community Events