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

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

In which version it would be implemented?

Yeah!!!

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

+1

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='#';

This has always seemed like an odd oversight to me

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

Unbelivable, that this is still open

This is no improvement, it is simply a bug, that this is not possible

I just need to edit a typo in the description. Is there a way to do that?

Mark Michaelis described an excellent workaround in JRA-8620 which I copy here for casual browsers:

1. Create a Security Level "Tmp"
2. Delete the Security Level you want to rename or edit the description of
3. As replacement-security level select "Tmp"
4. Create the new Security Level with e. g. adjusted description or name
5. Delete "Tmp" and select as replacement-security level the newly created Security Level.

Come on Atlassian, this is basic consistency and anyone would regard it as a quality issue...

I've had some discussions with Atlassian's support about this ticket. The basic situation is that they will only implement this if this ticket gets enough votes to make it to the top of the list of most voted-on tickets. If you look for open tickets sorted by votes this ticket appears to be around number 150. By comparison the topmost item is 9 years old and has over 1100 more votes than this ticket.

Is this going to be done?

What is the status of this ticket? It appears to have been open since 2005 without seeing any activity. As a paying customer of JIRA OnDemand I sorely miss this feature.

This is not a duplicate of JRA-12828

This is an easy but important one!

Come on, seriously, don't tell me that you don't have a numeric ID and that is why you don't allow editions

At least, let us edit the Description, please...

It seems there are many plugins/extensions that rely upon the configuration of security levels.

unfortunately if you implement issue level security and integrate this with the jira misc workflow extension (so you can get default issue levels on creation), then every time you "edit" the issue security levels by deleting and adding them, you have to reconfigure all of the workflows.

Renaming and changing descriptions of security levels is a basic function which would be incredibly useful to a ton of people. Nothing more frustrating than creating a security level and setting it all up only to discover a typo in the description.

Editing the Name and Description of a Security Level is not very business user friendly. We have a JIRA Hosted version and we will need to open a support ticket to do that. Would be great to have the Edit functionality.

My solution for now is to change the description in database directly, which is MySQL I using and operation easy.

This would seem to be a very easy fix as the levels are stored by ID and not using the level name as a key. Please spend 5 minutes on this and fix it!

It would also be useful to set the default order of Security levels in the drop-down.

Just a hint: A workaround is described in the duplicate issue JRA-8620.

Delete operation should also be moved to the Operations column.