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

Group names aren't allowed to have commas, interface doesn't warn about this

XMLWordPrintable

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

      Apparently groups names aren't allowed to have commas in them; however, the Group Browser interface happily lets you create groups that have commas in their names.

      So I am not sure if the bug is that the interface allows you to create the name with commas in it or instead the bug is that you can't assign a group that has commas in its name to a Project Role. The delimiter is a comma so it thinks you are adding multiple groups to the Project Role.

      For example, I have a group named "appdev-team1,5,6". When I add this to a Project Role it thinks I am assigning group "appdev-team1" and "5" and "6" to the project role (see screenshot)

        1. Screen shot 2010-07-26 at 12.36.40 PM.png
          Screen shot 2010-07-26 at 12.36.40 PM.png
          11 kB

            [JRASERVER-21862] Group names aren't allowed to have commas, interface doesn't warn about this

            Roy Krishna (Inactive) added a comment -

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Roy Krishna and Josh Devenny
            JIRA Product Management

            Roy Krishna (Inactive) added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Roy Krishna and Josh Devenny JIRA Product Management

              Unassigned Unassigned
              19cf9974e13a Michael
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: