• Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Answered
    • Affects Version/s: 6.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • 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.


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


      We use the Jira for project management and we adopt Category as "Customer".
      Now I need migrate our defects management from Bugzilla to Jira.

      In our process, components and versions are attributes of "products" (products are the systems resulting from our projects). In other words, we execute several projects to improve the same product!

      I think that we should not duplicate all the versions and components configurations for each new project of the same product...

      The subcomponents solution have the same problem... all structure (components/subcomponents) are exclusive to one unique project...

      I think that if the Jira had projects hierarchy, we can use the level 1 as product and project level 1.1 as project, with components reuse (as the Mantis tool can do). Or something like it.

      What's your current position about this issue JRA-12241?

      What solution do you indicate to my need?

      Thanks a lot!


          Issue Links



              • Assignee:
                ricardo.antunes Ricardo Antunes
              • Votes:
                1 Vote for this issue
                4 Start watching this issue


                • Created: