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

      Raised for jira-root@3SOFT.de

      ---------------------------------------------------------
      PLEASE support this feature.

      We add new groups to restrict sets of users to certain projects (and we have many projects and many groups and many users in them).

      And there is no way to correct typos (without direct database/XML access).

      Imagine the following scenario.

      1) add new groups: projectname-customer-role
      (e.g. foobar-birch-telecom-tester, foobar-birch-telecom-developer, ...)
      2) add around 30 user to the various groups

      3) make new schemes (issue,notification,permission,....) for a new "special" project
      4) add the new project – assign the schemes ....

      5) launch the new project
      6) two weeks later you get the info from one user
      "hey man - I'm in the group "foobar-bitch-telcom-tests" it's not bitch it's birch ....
      7) Now how should we help the user to get out of a group of bitchs?

      ???

      NB: In this support request screen there is a small description below this big textarea and this description is wrong (here we should not "Enter a one-line summary of the problem"

            [JRASERVER-5460] Rename support of groups/users

            BR DevOps made changes -
            Link New: This issue duplicates JRASERVER-72769 [ JRASERVER-72769 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3054117 ] New: JAC Suggestion Workflow 3 [ 3684036 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2604574 ] New: JAC Suggestion Workflow [ 3054117 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2555180 ] New: Confluence Workflow - Public Facing v4 [ 2604574 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2344922 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2555180 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2112541 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2344922 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2085756 ] New: JIRA Bug Workflow w Kanban v6 [ 2112541 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 887474 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2085756 ]
            Hannes Obweger (Inactive) made changes -
            Component/s New: User Management - Others [ 10125 ]
            Component/s Original: Administration [Deprecated] [ 10271 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 717943 ] New: JIRA Bug Workflow w Kanban v6 [ 887474 ]

              Unassigned Unassigned
              mark@atlassian.com MarkC
              Votes:
              8 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: