Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Duplicate
    • Affects Version/s: 3.0 Pro Preview
    • Fix Version/s: None
    • Component/s: Backend / Domain Model
    • Labels:
      None
    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      Currently once a person's username is chosen (eg. 'jefft'), it can't be changed. We should write a 'rename user' function, accessible to administrators.

        Issue Links

          Activity

          Hide
          brian@atlassian.com Brian Nguyen added a comment -

          Hi Everyone,

          I'm just cleaning up this duplicate issue, and resolving it. So for those who have voted or are watching this issue, this issue is now being tracked at JRA-1549

          Thanks,
          Brian

          Show
          brian@atlassian.com Brian Nguyen added a comment - Hi Everyone, I'm just cleaning up this duplicate issue, and resolving it. So for those who have voted or are watching this issue, this issue is now being tracked at JRA-1549 Thanks, Brian
          Hide
          adam.cameron Adam Cameron added a comment -

          Respectfully, Jeff, I think I understand the issue completely, and YOUR response seems to be missing the gist of the issue and the subsequent discussion.

          I was asking questions specifically directed at your justification (which I do not think is really very good, to be honest) of why you've done the user schema the way you have.

          Nowhere against this issue has anyone mentioned anything about priorities until you piped up with your somewhat non-sequitur response to my last three questions.

          Show
          adam.cameron Adam Cameron added a comment - Respectfully, Jeff, I think I understand the issue completely, and YOUR response seems to be missing the gist of the issue and the subsequent discussion. I was asking questions specifically directed at your justification (which I do not think is really very good, to be honest) of why you've done the user schema the way you have. Nowhere against this issue has anyone mentioned anything about priorities until you piped up with your somewhat non-sequitur response to my last three questions.
          Hide
          anton@atlassian.com Anton Mazkovoi [Atlassian] added a comment -

          Adam,

          I have added a comment to JRA-1549 regarding this improvement. We see that this issue is important - Jeff was trying to say that the most difficult thing we have to do is prioritise between improvements.

          Thanks,
          Anton

          Show
          anton@atlassian.com Anton Mazkovoi [Atlassian] added a comment - Adam, I have added a comment to JRA-1549 regarding this improvement. We see that this issue is important - Jeff was trying to say that the most difficult thing we have to do is prioritise between improvements. Thanks, Anton
          Hide
          osiega IT Omnitracs added a comment -

          Just installed v6.0 rc1 over v5.x
          Wanted to rename a username but the field is not there for username.

          Did i forget something?

          Show
          osiega IT Omnitracs added a comment - Just installed v6.0 rc1 over v5.x Wanted to rename a username but the field is not there for username. Did i forget something?
          Hide
          dpaquet CIEp added a comment -

          I confirm the same issue here with the released version of jira 6.

          Still not working on 6.0.6

          Show
          dpaquet CIEp added a comment - I confirm the same issue here with the released version of jira 6. Still not working on 6.0.6

            People

            • Assignee:
              Unassigned
              Reporter:
              jefft Jeff Turner
            • Votes:
              29 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: