Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-38002

Connect comments made in WF transition screen to change history (status)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • 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.

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

      Author, watcher or any other participiant of issue want to know the reason of why issue was resolved, re-opened or transmitted between statuses. Generally comment field is used to fill such type of info. So, the only way for user to find out what exact comment was added during any particular transition is to correlate time of comment and transition.
      More simply there is no way to write such sql-statement (tables jiraaction, changegroup, changeitem)

            [JRASERVER-38002] Connect comments made in WF transition screen to change history (status)

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3045633 ] New: JAC Suggestion Workflow 3 [ 3686705 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2608888 ] New: JAC Suggestion Workflow [ 3045633 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]

            Gosia Kowalska added a comment -
            Atlassian Update – 20 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 20 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2592531 ] New: Confluence Workflow - Public Facing v4 [ 2608888 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2355683 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2592531 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2123024 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2355683 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2084851 ] New: JIRA Bug Workflow w Kanban v6 [ 2123024 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 875087 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2084851 ]
            jonah (Inactive) made changes -
            Description Original: Author, watcher or any other participiant of issue want to know the reason of why issue was resolved, re-opened or transmitted between statuses. Generally comment field is used to fill such type of info. So, the only way for user to find out what exact comment was added during any particular transition is to correlate time of comment and transition.
            More simply there is no way to write such sql-statement (tables jiraaction, changegroup, changeitem)
            		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-38002].
              {panel}

            Author, watcher or any other participiant of issue want to know the reason of why issue was resolved, re-opened or transmitted between statuses. Generally comment field is used to fill such type of info. So, the only way for user to find out what exact comment was added during any particular transition is to correlate time of comment and transition.
            More simply there is no way to write such sql-statement (tables jiraaction, changegroup, changeitem)

              Unassigned Unassigned
              2d9f5866d996 ArturP
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: