Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Attachments are not saved when used with the jira.issue.editable state property setting

lintek214 October 22, 2022

I want overall field security when my issues are in the "in-progress" states. I have three of them, IN-WORK, FINISHED, and VERIFY. For each state I set the state property "jira.issue.editable=false".

When transitions into each of those states occur, I have created transition screens to allow edits. In each screen, the Attachments field is available. When I make any field edit on those screens, the change is saved and visible after the transition except for adding attachments. I see the attachment upload progress bar. So, it appears to work, but after the transition is finished and the VIEW screen is displayed, the attachment is not visible.

I'm sure if I removed the state property, the attachment(s) are going to show again. 

This seems to be a bug where attachment are not being save in the transition screen or during the transition processing as the other fields.

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 23, 2022

There is a bug here, I think, but it's not the one most would be thinking of.

The attachments "field" is not really a field (like Status and Issue type) - it looks like a field in some places, but it is a more complex system function. 

When it appears as a field, it obeys the rules on fields.  If you don't have "edit issue", then you can't use it.  The bug is that it is offered to you (without any warning that you can't actually use it) when there's no editing allowed, not that it ignores what you put stuff in!

lintek214 October 23, 2022

Yes, I can understand what you have said. I had a thought that if I switched to the old view, I wondered what would be displayed on the VIEW screen. Sure enough, in the old view with the "jira.issue.editable = disable" set, the attachment area is not displayed. That's when I came to conclusion that what I was seeing in the transition screen really should not have been there and the upload function was really failing.

With all that discovered and said, from a process point of view, shouldn't attachments be allowed all the time? Just like comments, attachment won't really change the nature of the documented reason in the issue. I consider them external artifacts.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events