|
History
| Log In
|
|
|
|
Since deleting an attachment is a 'permanent' removal of information, much like deleting an issue, I can see how an argument could be made to support the current implementation where user must have issue delete permission to delete an attachment. The problem is where users need to delete attachments they have added themselves - especially where they need to replace a file with the same name (e.g. a sql script) and make sure no-one accidentally reads the old file. Here's an idea that could address all concerns. Anyone who has permission to add an attachment would inherently also have permission to Hide an attachment. Hiding an attachment is different from deleting one in that it is still there, but available for only some to see. The user interface could still say "Delete" so the end user thinks they are deleting it, but it is merely marked as hidden on the issue, so it is still physically there. However, to a user with "Delete Issue" permission (typically an administrator), they would see ALL attachments, including the hidden ones, and be presented with a vsiual cue indicating which ones were marked as deleted, and an option to "Permanently Delete" those attachments. So, to most end users, they can delete attachments, but without the risk of permanently deleting irretrievable information.
I very much like Neal's proposed solution to this issue.
This is a needed feature in our shop and this would also prompt the need to have user and admin level attachment search ability.
users may know the name (or part) of a file but not the issue key-# and want to delete the attachment from the issue. currently there isn't any way of locating a issue via an associated attachment name.
Some feedback from a customer:
Management of attachments is not flexible. You need to give a user the "Delete Issues" permission to be able to manage attahments. A much better solution would be to implement a new permission "Manage Attachments". Today, all our users can add attachments to an issue, but they cannot delete them afterwards. I agree with Ernest, it would be nice if managing attachments was seperate from managing issues, and that we could be flexible and add a higher level of granularity to global permissions.
This seems like a very worthwhile investment and a constant pain that my company sees while using the product. We are at odds in the sense that we need to only show the relevant version of a PRD (product requiement document) rather than 10 versions of a PRD and we are allowing users the ability to completely erase a ticket when we only want to allow them the ability to manage their attachments better. If a user does delete an attachment, it would be preferable if that attachment was simply tagged hidden instead of actually being deleted.
Regardless of it were "hiding" a file or deleting it, a higher level of permission granularity would be a huge upgrade for this particular set of functionality.
One workaround is to keep attachments on a server, and only include the link in the issue. Of course, that will not work for everyone - the people need access to the link from wherever they are running JIRA from.
See Unfortunately I can only vote once for this issue 
I also thought I created an improvement request months ago to have the issue navigator with a column that identifies which issues have attachments, to work like Microsoft Outlook (and probably other e-mail clients), where you can filter on and sort on issues based on whether they have an attachment or not. A paper clip icon in the column to indicate attachment(s) like Outlook would be great. The "Images" column doesn't accomplish the same thing since all you need is an indicator, and it won't work on non image attachments and you cant filter on it etc. It will be nice to have all delete permission separated too. Now JIRA (3.3.3) only have one delete permission that agroups the posibility to delete attachments,comments and issues. i thinks it will be nice to have these permission separated because now delete opetacion a fisical and not logical
One of the things we really wish Jira supported is the ability to manage (your own) comments, attachments, and delete issues as separate permission schemes.
There are already issues created for this so I won't raise a new one, but will briefly comment as to why this is important to us. Firstly, we don't want to give users 'delete' permissions to delete an issue, only an administrator should ever have permission to permanently delete an issue imho. However, quite often a user will upload the wrong attachment, or need to replace an attachment, and they then have no way of changing this. This is a problem. A second problem, is that users will quite often make a typo in the comment, or comment on the wrong issue, and then they have no means of editing or deleting their own comment. This is also a problem. It would be great to have a separate 'super delete' permission scheme, as well as a 'manage attachments/comments' permission scheme. Hi,
Many user ask me to delete attachments because of errors or updates. So I hope that this possibility to give this permission to specifics users will come soon as possible. Thanks We have the same problem. We have had to assign "super-users" throughout the organisation to be able to delete the erronous attachments. We would prefer to have the delete attachment as a seperate role.
This issue has been around for ages! It's not assigned to anyone, has a very low priority, and has no indication of being fixed at all in the future. From my point of view this is very important: normal users should be able to manager their own attachments, comments, etc.
Please fix this in JIRA's next release! Priority? Come on, - they are developing calendar widgets!! who wants delete attachments??
Indeed, this issue is very old.
Deleting Issues was one of the first "new features" my users wanted to have after I introduced JIRA in my company! I can't see why this permission should be something very special. I guess this issue just dissapeared and was not reviewed a long time? My users need the ability to delete their comments, but not to delete their issues. These must be separated in the permission scheme.
This is a 3 years old issue that is not so difficult to implement!
Come on guys ... we are waiting for too long! This is critical for us. We are experiencing serious "attachment overload" and frankly I'm very, very disappointed that JIRA won't at least allow users to delete their own attachments. Consider all of these problems:
I can't keep up with the pace of "please delete the XYZ attachment" emails I'm getting. And worse, sometimes I go and delete the wrong attachment! Likewise, I can't give delete permission to users. That's just not allowed in our workflow, it's an administrator role. In the entire opinion of the users here at Practice Technologies, this is a bug and should be fixed immediately. Now we've got a VP in the organization getting involved:
This is really a bad situation. It needs to be fixed. Hey all -
We wanted the same functionality so I whipped up a plugin based on Philip Herbst's Edit Comment Plugin Check it out: All it does is allow users to delete their own attachments.. I will consider adding functionality to the plugin if there is a demand and if the requirements are exceptionaly clearly spelled out. Hi there.
I have similar requirements for this sort of thing:
The ability to delete one's own comments is more important to me than the others, but I've just had a chance where one of my middle-level users has attached something to an issue, and now need to update it, but cannot, as it's not apporpriate for that user to be able to delete issues or comments (other than their own ones JIRA 3.9 is planned to be released in May.
Administrators (as of JIRA 3.9) can now grant users the right to delete their own attachments and to delete others attachments, rather than having a general "create attachments" permission.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Resolved
Minor
Separate "delete attachment" permission
Same for comments.