Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-13498

On Epic Creation, Give Option to Have Epic Name Default to Summary

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 1
    • 30

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

      As an administrator, it would be valuable to have the option to have Epic Name always default to the value of the Summary field (since they are often the same), upon Epic Creation. Currently, this cannot be done via workflow, as the only way to do this would be via post function, which would require the transition to take place before the post function was triggered.

            [JSWCLOUD-13498] On Epic Creation, Give Option to Have Epic Name Default to Summary

            April Villone added a comment -

            This recently became an issue for our company.  We have no desire to need to enter the name of our ticket twice.  Please make this a priority. 

            April Villone added a comment - This recently became an issue for our company.  We have no desire to need to enter the name of our ticket twice.  Please make this a priority. 

            Christopher Busch added a comment -

            I like Jira, but the team's tone deafness for completing sensible sane features is maddening.  

            If one looks at https://jira.atlassian.com/browse/JSW-11128, one can see a terse answer.

            "Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time."

            Jira, when you leave out sensible defaults, it adds a lot of busy work and makes the product lack fit and finish and look slap-dash. The product needs to look at user productivity by eliminating clicks and typing as much as possible.  We are all extremely busy.

            Christopher Busch added a comment - I like Jira, but the team's tone deafness for completing sensible sane features is maddening.   If one looks at https://jira.atlassian.com/browse/JSW-11128 , one can see a terse answer. "Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time." Jira, when you leave out sensible defaults, it adds a lot of busy work and makes the product lack fit and finish and look slap-dash. The product needs to look at user productivity by eliminating clicks and typing as much as possible.  We are all extremely busy.

            Daniel Holmes added a comment -

            Aldo related to JRA-41733

            Daniel Holmes added a comment - Aldo related to JRA-41733

            Daniel Holmes added a comment -

            Previously asked for by JSW-11128

            Daniel Holmes added a comment - Previously asked for by JSW-11128

              Unassigned Unassigned
              efranklin Eric Franklin (Inactive)
              Votes:
              32 Vote for this issue
              Watchers:
              34 Start watching this issue

                Created:
                Updated: