Permission on project schema level for attachment field

Question

Hi team,

We are trying to synchronize attachment field in HP ALM and in repo JIRA project for bugs (JIRA version used (v6.4.11#64026-sha1:78f6ec4) )

With a sync tool from ALM, we see attachment field in JIRA is read only. However, any user of that project can add or remove attachment in bugs. JIRA team here also confirmed that the attachment setting is on.

We and HP ALM team made some rest calls:

/rest/api/2/issue/<issuekey>/edimeta ( e.g. rest/api/2/issue/JAS-1/editmeta )

/rest/api/2/issue/createmeta?projectKeys=JAS&expand=projects.issuetypes.fields

and from the .json files we received, it does not contain attachment field in it, they suggested that the permission might be restricted on project schema level.

Could you please suggest what needs to be done by or JIRA admin?

Where can our JIRA admin check this setting and made some change, if necessary?

Thank you very much in advance.

Benjamin Weinheimer-Erben _mgm-tp_ · Answer

Hi Amiril,

they should check the Project Roles via: "JIRA Administration" --> "User Management" --> search for the User you use for API-Access --> click on "Project Roles".

If they know which Role your user has in the project in question, they can review the given permission within the Permission Scheme of the project in question. Here your user should be in a role that have the "Create Attachment" permission.

greetings

Benjamin

Petar Petrov _Appfire_ · Answer

Assuming that you do NOT want users to be able to attach files, the place that the admins need to look at is the permission scheme for the project and specifically the "Create Attachments" permission. Let me know if this is not what you are looking for.

The easiest way to find out if a user has a given permission is by using the Permission Helper administrative page.