Allow Project Admins to delete an option
Issue #66
resolved
Currently Project Admins can only disable options. Deletion is only possible for System Admins.
As this add-on is perfect for the use-case to provide project admins, the ability to configure their project specific fields without the need to give them System Admin rights, they should also be able to delete options.
The consequences should just be the same ("Note: Deleting a custom field option removes all matching values from all issues.")
Comments (20)
-
repo owner
-
reporter
Oh ok that is very good to know, thank you for that ! :) We will use that.
Best regards, Markus
-
repo owner
I have a new very ready, which provides possibility to delete an option (and automatically removes it from all related issues). @markusd1, Would you be available for a test of the new version?
Best regards, Holger
-
repo owner
- changed milestone to 2.6.0
-
reporter
Hello Holger, oh waow that sounds great, of course I would be available for a test of the new version. Thank you in advance. Best regards, Markus
-
repo owner
You can find the version 2.6.0 here for manual download https://bitbucket.org/hski/projectspecificselectfield-public/downloads/
Then use addon manager in Jira to install this version via file upload as described here https://confluence.atlassian.com/upm/installing-add-ons-273875715.html#Installingadd-ons-Installingbyfileupload
Please test in a save test environment, not in your production environment.
From functionally perspective, this 2.6.0 is complete and tested. But would be great if you could check layout of the delete confirmation dialog with your typical web browser and operation system. I checked with Chrome and Firefox. Maybe you can check with Internet Explorer or whatever is in use at your company. Would be nice if you could paste a screenshot here in this issue.
Thanks, Holger
-
reporter
Hello Holger,
for the link https://bitbucket.org/hski/projectspecificselectfield-public/downloads/ , I get an "Access denied" message. Yes we use Chrome and IE 11 and we will test it using both.
Best regards, Markus
-
repo owner
- attached jpssf-2.6.0.jar
Okay, please find the addon package attached to the issue.
-
reporter
Thank you for the jar. I did some tests, unfortunately the new delete button did not work. Everything else (like edit, add etc.) worked fine. With both Browsers (Chrome v66, IE 11), when pressing "Delete" a blank white dialog appeared, and I could only continue pressing "Esc" on the keyboard. Afterwards nothing has changed. I will attach two screenshots. If I can be of further help, please let me know. Best regards, Markus
-
repo owner
Does it work in Chrome?
-
reporter
No, it is the same behaviour with both browsers.
-
repo owner
- attached jpssf-2.6.0.jar
I am very sorry! I accentially included a small HTML change, but this introduced an error in the respective JavaScript for delete function. I fixed this issue and attached a new package here. Would be great, if you could test again layout with your prefered browser.
Best regards, Holger
-
reporter
Thank you very much for the update. Now it works great in both browsers (IE11 and Chrome) (y)
Just two feedback topics: 1) The removement not visible in the issue history. The action is also not visible in the audit log. As a bulk change is visible in the issue history it would be great if the action is visible somewhere. Possible Options: Audit log would be sufficient. If it acts like bulk change with issue history the change should not send emails.
2) Would be really great if the pop-up contains the information how many issues are affected. The system admin screen shows even the issue-keys, this is too much for the pop-up. But if possible, just the number of affected issues would be awesome.
Best regards, Markus
-
repo owner
Thanks for the feedback!
Regarding 1) to have nothing in issue history is standard behaviour in Jira and also the same for renaming. Same behavior also for components and versions by the way.
Will look how to add this info to audit log.
Regarding 2) will look at it. It may be in general a good idea to have number of issues in the configuration table for the option values and not only in the delete popup.
How urgent do you need this e.g. 2) could be postponed to a later version?
-
reporter
Thank you, that sounds great. Yes of course, that is fine also in a later version. Best regards, Markus
-
repo owner
Sorry, had a typo in the above comment.
Do you really think for 1) an entry in audit log will be a useful implementation? It is only possible to access by Jira admins, not project admins. And typically it is not recorded for option value changes by Jira admins via the regular option values context manager.
-
reporter
If it is too complicated, it is not a must have. It would just be useful if a project admin accidentally deletes an option and noone knows what happend, and why maybe hundreds of issues lost an information. For example we even had a case, where a confluence space was deleted by a space admin by accident. And we (system admins) were very happy to have something in the logs to be able to understand what happened. So everything happens :) But you are of course right, same as for components or releases, when they are gone they are gone. So it would also be totally fine without. BR Markus
-
repo owner
- changed status to resolved
Version 2.6.0 released.
-
reporter
Works perfectly thumbs up
-
repo owner
Thanks for the feedback. :-)
Would be awesome if you could take 5 min to enter a short comment and vote at Atlassian Marketplace for my plugin.
Best regards, Holger
- Log in to comment
Thanks for your feedback! Yes, I understand the demand behind your request. I just wanted to avoid to implement the necessary bulk chage of the related issues.
But if you as project admin remove the option value from issues on your own via bulk change and then open the bar chart page with the different fields and option values, there is a background cleanup process to remove all disabled option values who have no issues assigned to it.
Maybe this helps a little as a workaround.