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

Should be able to 'edit' Security Levels

XMLWordPrintable

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

      Atlassian Update - 11 May 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. After review, the JIRA bugfix team has decided to make this bug a priority and will be addressing it in the near future. We're hoping to have it released soon.

      Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      It should be possible to edit Security Level information (name and description). Currently, to change the name or description a new level must be created.

            [JRASERVER-8042] Should be able to 'edit' Security Levels

            Martin Hynek added a comment -

            This is fixed after 11 years?! Really?! Sorry guys but there are only two options why it tooks soo long.. You have lack of developers or your development management has totally failed... Sorry for commenting closed and fixed issue, but ...

            Thx kesar for pointing table where it's stored...

            Martin Hynek added a comment - This is fixed after 11 years?! Really?! Sorry guys but there are only two options why it tooks soo long.. You have lack of developers or your development management has totally failed... Sorry for commenting closed and fixed issue, but ... Thx kesar for pointing table where it's stored...

            Oswaldo Hernandez (Inactive) added a comment -

            Hi all,

            This improvement has already been implemented by the development team and should ship in the next JIRA Cloud update which we estimate to deliver next Monday 18th of January 2016.
            JIRA Server customers will get this improvement in the JIRA 7.1.0 Server Release.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi all, This improvement has already been implemented by the development team and should ship in the next JIRA Cloud update which we estimate to deliver next Monday 18th of January 2016. JIRA Server customers will get this improvement in the JIRA 7.1.0 Server Release. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Maik Winter added a comment -

            In which version is the issue fixed now?

            Maik Winter added a comment - In which version is the issue fixed now?

            Olga Plisko added a comment -

            In which version it would be implemented?

            Olga Plisko added a comment - In which version it would be implemented?

            Susan Hauth [Jira Queen] added a comment -

            Yeah!!!

            Susan Hauth [Jira Queen] added a comment - Yeah!!!

            Dave Meyer added a comment -

            Hi everyone,

            After review, the JIRA bugfix team has decided to make this bug a priority and will be addressing it in the near future. We're hoping to have it released soon.

            Please don't hesitate to contact me if you have any questions.

            Regards,
            Dave Meyer
            Product Manager, JIRA Platform

            Dave Meyer added a comment - Hi everyone, After review, the JIRA bugfix team has decided to make this bug a priority and will be addressing it in the near future. We're hoping to have it released soon. Please don't hesitate to contact me if you have any questions. Regards, Dave Meyer Product Manager, JIRA Platform

            Tom104Tom added a comment -

            +1

            Tom104Tom added a comment - +1

            ArtoK added a comment - - edited

            Almost 10 years!

            Descriptions are in table 'schemeissuesecuritylevels' in the database, so check your security schemes id: 

            SELECT * FROM schemeissuesecuritylevels;

            Update the description (replace # with the correct id number): 

            UPDATE schemeissuesecuritylevels SET description='new description' WHERE id='#';

            ArtoK added a comment - - edited Almost 10 years! Descriptions are in table 'schemeissuesecuritylevels' in the database, so check your security schemes id: SELECT * FROM schemeissuesecuritylevels; Update the description (replace # with the correct id number): UPDATE schemeissuesecuritylevels SET description= ' new description' WHERE id= '#' ;

            MattS added a comment -

            This has always seemed like an odd oversight to me

            MattS added a comment - This has always seemed like an odd oversight to me

            David Vega added a comment -

            I agree, this should be reclassified as a bug (defect)

            David Vega added a comment - I agree, this should be reclassified as a bug (defect)

              kcichocki K (Inactive)
              a10d110f3c3b Jason Dillon
              Votes:
              131 Vote for this issue
              Watchers:
              84 Start watching this issue

                Created:
                Updated:
                Resolved: