• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Your products lack one type of a product - something that would allow us to create software architecture models, like Enterprise Architect:

      At the moment we're forced to use detached systems to actually model a solution and track issues.

      It would be nice if there would be one centralized system that would allow us to document software, manage requirements and design solutions.

       

      Something like Atlassian JIRA + Atlassian Confluence + Enterprise Architect in one package, so we can:
      • Document requirements:epics, user stories, generic requirements, something like this:
      https://i.imgur.com/d35vf9N.png

      • Create a model of a solution using UML(not just a bunch of unrelated diagrams)

      • Based on a model, create dashboards, sprints, iterations, releases, tasks and other work items issue trackers like Youtrack and JIRA allow us to create depending on what development process we use.

       

      It would be nice to have an all-in-one system that can do what Enterprise Architect allows you to do and what JIRA allows us to do with all the benefits: create models specific to iterations. So let's say I create a model for iteration one and start working on a model for iteration 2 based on model from iteration 1 and user stories for iteration2. Then we decide to move a user story from iteration 2 to iteration 1, so I change the model for iteration 1 respectively, and system automatically adds these changes to iteration 2, so I don't have to edit model twice for 2 iterations.
      Then we would be able to link model elements(diagrams, UML elements such as components, classes, use cases, etc) and issues. Right now you can only create unrelated diagrams and link them to issues with extensions like SmartDraw:

       

      But that's far from actual modeling because you can't actually create full models and link work items to components of the solution model.

      What do you think about this idea?

            [JRACLOUD-72868] all-in-one application lifecycle management system?

            Atlassian Update - August 30, 2021

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - August 30, 2021 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              59dcd2521832 Sergei Kulagin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: