-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
Problem Definition
Archived issues are marked as read-only:
Issues will be read-only and accessible only with a direct link, mentions in other issues or applications, or on the Archived issues page (Issues > Archived issues). You won't be able to modify them but for audit purposes you can view or, if you're a Jira system admin, export them to a CSV file.
from Archiving an issue
When a user attempts to delete an archived issue via REST, the action fails and an error is returned stating that the operation is not permitted.
Â
Suggested Solution
The user would be able to delete the issue.
Possible implementation:
from focusedCommentId=2354315
maybe introduce a feature (say Purge) which are only executed on Archived Issues to enable use cases allowing getting rid of issues from the system permanently. Again this should be a bulk feature similar to Archive where users are allowed to perform the function via similar methodologies like archive.
Workaround
So far, the only workaround that has been found is to restore the issue, then delete it.
- is related to
-
JRASERVER-74581 Deleting an issue with many sub-tasks is slow and affects cluster performance
- Gathering Impact
-
JRASERVER-70604 Cloning an archived issue fails
- Gathering Impact
-
JRASERVER-70162 Ability to auto-delete Archived issues
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...