Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-1549

Ability to rename a user

XMLWordPrintable

    • 297

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

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

      Atlassian Status as of 22 May 2013

      Hi everyone,

      Thanks so much for your votes and comments on this issue.

      JIRA 6.0 has been released with the ability to edit usernames and we all hope you take it for a spin! JIRA 6.0 contains lots of other goodness and you can read the full release notes here.

      Cheers,

      Roy
      JIRA Product Management
      roy at atlassian dot com

        1. update_username_jira_6.2.6.sql
          2 kB
        2. TableDataSearch.sql
          2 kB
        3. TableData Find and Replace.sql
          2 kB
        4. Search_list.csv
          1 kB
        5. screenshot-1.jpg
          screenshot-1.jpg
          21 kB
        6. renameuser.sql
          2 kB
        7. OracleDB-UserNameUpdate-SQL-Jira3.13.4-Enterprise.txt
          7 kB
        8. jira_user_migration 5.2.sql
          4 kB
        9. jira_user_migration_5.2_Postgresql_9.2.sql
          6 kB
        10. jira_user_migration_5.2_Postgresql_9.2_v2.sql
          6 kB
        11. jira_renameuser_all.sql
          4 kB
        12. edit_username.png
          edit_username.png
          145 kB
        13. Edit_Profile_615.png
          Edit_Profile_615.png
          61 kB
        14. D3904554-8F1C-8F48-9B44-FF092AD4E845
          7 kB
        15. D3904554-8F1C-8F48-9B44-FF092AD4E845
          7 kB
        16. D3904554-8F1C-8F48-9B44-FF092AD4E845
          7 kB
        17. D3904554-8F1C-8F48-9B44-FF092AD4E845
          7 kB
        18. D3904554-8F1C-8F48-9B44-FF092AD4E845
          7 kB

            [JRACLOUD-1549] Ability to rename a user

            Yatish Madhav added a comment -

            Hi - I wonder if I am the only one noticing this. Doubt so. I see this is for Jira Cloud but the workaround answer "Atlassian Status as of 22 May 2013" is for Jira Server? Am I right?

            Please advise? Thank you

            Yatish Madhav added a comment - Hi - I wonder if I am the only one noticing this. Doubt so. I see this is for Jira Cloud but the workaround answer "Atlassian Status as of 22 May 2013" is for Jira Server? Am I right? Please advise? Thank you

            Yatish Madhav added a comment -

            Hi - I wonder if I am the only one noticing this. Doubt so. I see this is for Jira Cloud but the workaround answer "Atlassian Status as of 22 May 2013" is for Jira Server? Am I right?

            Please advise? Thank you

            Yatish Madhav added a comment - Hi - I wonder if I am the only one noticing this. Doubt so. I see this is for Jira Cloud but the workaround answer "Atlassian Status as of 22 May 2013" is for Jira Server? Am I right? Please advise? Thank you
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3155848 ] New: JAC Suggestion Workflow 3 [ 3651304 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336248 ] New: JAC Suggestion Workflow [ 3155848 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2101227 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336248 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2063488 ] New: JIRA Bug Workflow w Kanban v6 [ 2101227 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 1868457 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2063488 ]
            jonah (Inactive) made changes -
            Description Original: {panel:title=Atlassian Status as of 22 May 2013|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
            Hi everyone,

            Thanks so much for your votes and comments on this issue.

            JIRA 6.0 has been released with the ability to edit usernames and we all hope you take it for a spin! JIRA 6.0 contains lots of other goodness and you can read the full release notes [here|https://confluence.atlassian.com/display/JIRA/JIRA+6.0+Release+Notes].

            Cheers,

            Roy
            JIRA Product Management
            roy at atlassian dot com

            {panel}             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-1549].
              {panel}

            {panel:title=Atlassian Status as of 22 May 2013|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
            Hi everyone,

            Thanks so much for your votes and comments on this issue.

            JIRA 6.0 has been released with the ability to edit usernames and we all hope you take it for a spin! JIRA 6.0 contains lots of other goodness and you can read the full release notes [here|https://confluence.atlassian.com/display/JIRA/JIRA+6.0+Release+Notes].

            Cheers,

            Roy
            JIRA Product Management
            roy at atlassian dot com

            {panel}
            jonah (Inactive) made changes -
            Link New: This issue is related to JRASERVER-1549 [ JRASERVER-1549 ]
            vkharisma made changes -
            Link New: This issue causes JSWCLOUD-7269 [ JSWCLOUD-7269 ]

              pwyatt Penny Wyatt (On Leave to July 2021)
              8397740ea872 Michael Phillimore-Brown
              Votes:
              786 Vote for this issue
              Watchers:
              398 Start watching this issue

                Created:
                Updated:
                Resolved: