• 0
    • 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.

      There is significant confusion around 'Title' vs 'Summary'  e.g. Solved: Meaning of Description, Summary, Text.. etc. (atlassian.com)  in part i believe this is because within a Jira ticket, 'summary is placed where universally you would expect to see a title... (at the very top)

      Further, this is more of a problem especially in Roadmaps where this uses 'Summary' field rather than the Title -  Summaries are typically sentences or paragraphs long, and are completely not suitable to identify Issues in a ~1 inch space on a gantt chart.    This should really be 'Issue Title', although i suspect the difficulty will be because you have names the fields 'Epic Title', 'Story Title' etc. which makes it more difficult?

      My suggestions are therefore:

      1 - allow configuration of the Title to be used within Roadmaps, rather than default 'summary'
      2 - allow users to place 'Title' at the top of the page, and summary to be placed above 'description'

       

            [JSWSERVER-25181] Summary v Title - Roadmaps and Jira

            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

            Kerrie added a comment -

            Kerrie added a comment - https://atlassian.design/components/lozenge/examples

            thanks, have upvoted.

            btw, what are 'lozenges' except for a sticky cough sweet ?  

            gary carter added a comment - thanks, have upvoted. btw, what are 'lozenges' except for a sticky cough sweet ?  

            Kerrie added a comment - - edited

            I have created an Enhancement here https://jira.atlassian.com/browse/JPOSERVER-7244 to complement this one. Hopefully Atlassian will consider the two together and right this wrong

            Kerrie added a comment - - edited I have created an Enhancement here https://jira.atlassian.com/browse/JPOSERVER-7244 to complement this one. Hopefully Atlassian will consider the two together and right this wrong

            I totally agree with the comments by @Kerrie and @Keren Waters. Replacing the Epic Name (Epic Title) by the Epic Summary forced me to update all our epics to make the summary the same as the title/name. As mentioned above, both the summary and title have a different purpose.

            I hope the distinction between the longer summary and shorter title name will be introduced again in a way that does not add the complexity that - apparently - used to be in the software.

            Alex Hoogendoorn added a comment - I totally agree with the comments by @Kerrie and @Keren Waters. Replacing the Epic Name (Epic Title) by the Epic Summary forced me to update all our epics to make the summary the same as the title/name. As mentioned above, both the summary and title have a different purpose. I hope the distinction between the longer summary and shorter title name will be introduced again in a way that does not add the complexity that - apparently - used to be in the software.

            unless i am missing it, I don't appear to be able to edit my OP     if you are to raise a seperate thread though consider upvoting this and can return on yours too 

            gary carter added a comment - unless i am missing it, I don't appear to be able to edit my OP     if you are to raise a seperate thread though consider upvoting this and can return on yours too 

            Kerrie added a comment -

            Ah good spot Karen! I wonder if the OP @gary carter might consider adding that to this enhancement? If not i am happy to log a new one

            Kerrie added a comment - Ah good spot Karen! I wonder if the OP @gary carter might consider adding that to this enhancement? If not i am happy to log a new one

            The suggestion above only refers to showing Epic Summaries or Titles in Roadmaps.  This same issue now exists in Backlogs and Sprints due to a recent change by Atlassian to display Epic Summaries instead of Titles.  I agree with the suggestion but think it needs to be expanded to specify that Epic Title is used in Backlog and Sprint interfaces also.

            Karen Waters added a comment - The suggestion above only refers to showing Epic Summaries or Titles in Roadmaps.  This same issue now exists in Backlogs and Sprints due to a recent change by Atlassian to display Epic Summaries instead of Titles.  I agree with the suggestion but think it needs to be expanded to specify that Epic Title is used in Backlog and Sprint interfaces also.

            Kerrie added a comment -

            The forced change to displaying Epic Summaries instead of Epic Titles has been a frustration for our Team. I agree that a 'summary' by nature is a sentence or paragraph NOT a short Title for use in lozenges. 
            I understand Jira's desire to align things for company managed projects but forcing this change on all users with no configuration option was short sighted

            You even state 'That’s why we’re looking at providing you with the flexibility to shape our tools to the way you work' but what you have done is the opposite of providing flexibility! 

            Please provide a configuration option 

            Kerrie added a comment - The forced change to displaying Epic Summaries instead of Epic Titles has been a frustration for our Team. I agree that a 'summary' by nature is a sentence or paragraph NOT a short Title for use in lozenges.  I understand Jira's desire to align things for company managed projects but forcing this change on all users with no configuration option was short sighted You even state 'That’s why we’re looking at providing you with the flexibility to shape our tools to the way you work' but what you have done is the opposite of providing flexibility!  Please provide a configuration option 

              Unassigned Unassigned
              32dd7e3b7feb gary carter
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: