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

When reporter differs from creator, the creator should be recorded in change history

    XMLWordPrintable

Details

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

    Description

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

      Atlassian Status as of 3rd December 2013

      Hi everyone,

      Thanks so much for your votes and comments on this feature request.

      Good news, Everyone. Your waiting is about to end.

      Even though we had no plans to put the work related to this feature on our short term roadmaps, the solution was implemented as a result of "20% projects" effort and is currently being tested. You can read about our "20% projects" here: Life at Atlassian.

      The plan is to make this feature available with the next release of JIRA, which is targeted for the first quarter of calendar year 2014.

      Thanks for your patience and we hope you appreciate our open approach to feature requests.

      Regards,

      Roy Krishna & Bartek Gatz
      roy (at) atlassian (dot) com & bartek (at) atlassian (dot) com
      JIRA Product Managers


      Original request description:

      When a user creates an issue and sets the reporter to someone else, there is no record in the issue of who originally created the issue. We should record the actual reporter in the changelog.

      Attachments

        Issue Links

          incorporates

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-36247 Changing Reporter when creating ticket shows that person as the ticket creator

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-24119 Reporter loses change history when set to another user on create

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-34397 First reporter name being replaced in Activity Tab after change to new reporter

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-36247 Changing Reporter when creating ticket shows that person as the ticket creator

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-7919 Changelog should show issue creator as well as reporter

          • Closed

          Suggestion - JRASERVER-27778 Track Issue creator separately from Reporter

          • Closed

          Suggestion - JRASERVER-31308 Show the creator of an issue in the History tab

          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-34397 First reporter name being replaced in Activity Tab after change to new reporter

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-7919 Changelog should show issue creator as well as reporter

          • Closed

          Suggestion - JRASERVER-11125 JIRA 4.0 Enterprise Requirements

          • Closed
          relates to

          Suggestion - JRACLOUD-4618 When reporter differs from creator, the creator should be recorded in change history

          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              jwinters tier-0 grump
              7ee5c68a815f Jeff Turner
              Votes:
              64 Vote for this issue
              Watchers:
              47 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: