• 1
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Some customized agile solutions, i.e: scaled agile frameworks( SAFe, DaD and LeSS, etc..) are using terminology which is not fully supported with the Atlassian product line.

      Example:

      • You may want to structure your project hierarchy as  Epic > Feature > story but in Jira the structure is fixed for Epic > Story 

          Form Name

            [JSWSERVER-25127] Support terminology of scaled agile frameworks

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            rickywanglin1936230885 — I've noticed that the whitepaper signup page doesn't like autocomplete to fill out the fields, so if you manually enter your information, the download link should appear immediately.

             

            Apologies for the inconvenience! This issue has been reported to our marketing team for resolution.

            Chelsea C (Inactive) added a comment - rickywanglin1936230885  — I've noticed that the whitepaper signup page doesn't like autocomplete to fill out the fields, so if you manually enter your information, the download link should appear immediately.   Apologies for the inconvenience! This issue has been reported to our marketing team for resolution.

            Roi Fine (Inactive) added a comment - - edited

            Should be instantly. If you didn't get it, either try again or check your other email inbox folders.

            Roi Fine (Inactive) added a comment - - edited Should be instantly. If you didn't get it, either try again or check your other email inbox folders.

            Ricky Lin added a comment -

            Hi Roi,

            Thanks for the reply.  I read through the blog and have requested the white paper to see what it's like, but haven't received them yet.  Do you know how long it normally takes?

            Ricky Lin added a comment - Hi Roi, Thanks for the reply.  I read through the blog and have requested the white paper to see what it's like, but haven't received them yet.  Do you know how long it normally takes?

            Hi rickywanglin1936230885, please have a look at this blog:  https://www.atlassian.com/blog/agile/scaled-agile-atlassian-safe

            At the end of it, there is a link to a more detailed white paper on how to use Portfolio with scaled agile frameworks.

            Cheers,

            Roi Fine (Inactive) added a comment - Hi rickywanglin1936230885 , please have a look at this blog:  https://www.atlassian.com/blog/agile/scaled-agile-atlassian-safe At the end of it, there is a link to a more detailed white paper on how to use Portfolio with scaled agile frameworks. Cheers,

            Ricky Lin added a comment -

            Hey Roi.  Thanks - good to know that we aren't the only ones.  How has Atlassian suggested for other customers who have similar request to overcome this challenge currently?  What's the current best apporach to take to get as close to the hierarchy we want as possible?  Specifically, Epic > Feature > Story?  Should we create a separate issue type called "Feature" and link it to Epic / Story somehow?

            With the introduction of Jira Portfolio, there's the concept of Initiative > Epic > Story > Subtasks, but we cannot add anything in between Epic and Story to carry out this visualization for planning.

            I'd very much appreciate any feedback you may have.  If there's any kind of documentation or resource you might have can also help

             

            Ricky Lin added a comment - Hey Roi.  Thanks - good to know that we aren't the only ones.  How has Atlassian suggested for other customers who have similar request to overcome this challenge currently?  What's the current best apporach to take to get as close to the hierarchy we want as possible?  Specifically, Epic > Feature > Story?  Should we create a separate issue type called "Feature" and link it to Epic / Story somehow? With the introduction of Jira Portfolio, there's the concept of Initiative > Epic > Story > Subtasks, but we cannot add anything in between Epic and Story to carry out this visualization for planning. I'd very much appreciate any feedback you may have.  If there's any kind of documentation or resource you might have can also help  

            Hi rickywanglin1936230885, yes there other customers requesting better support for scaled agile concepts and terms. Please feel free to add the gaps in a comment on this ticket. Thank you!

            Roi Fine (Inactive) added a comment - Hi rickywanglin1936230885 , yes there other customers requesting better support for scaled agile concepts and terms. Please feel free to add the gaps in a comment on this ticket. Thank you!

            Ricky Lin added a comment -

            Roi -

            Thanks for opening up this ticket.  Do you have any other customers with similar requests?  What suggested workarounds do you have for our agile approach?  We have one of our new product owner currently dreading on the lack of hierarchy and wished we were using TFS instead.  I'm feeling a bit helpless in terms of how to make our team happy

            Ricky Lin added a comment - Roi - Thanks for opening up this ticket.  Do you have any other customers with similar requests?  What suggested workarounds do you have for our agile approach?  We have one of our new product owner currently dreading on the lack of hierarchy and wished we were using TFS instead.  I'm feeling a bit helpless in terms of how to make our team happy

              Unassigned Unassigned
              rfine Roi Fine (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: