Error in previously working Confiforms page: "Error communicating with Jira"

[Satyajit Shukre]

I have a Confluence page which uses Confiforms to accept requests from users. The page then communicates to Jira and a Jira ticket is raised with the same title and description and attachment. Also, the assignee is assigned to one of the users selected from a dropdown list. The Jira issue is raised as a story under a particular Epic for easy tracking. It was working fine for all users (and is working fine for me as well when I raise a test request) but when other users raise a request, they get the following error:

Error communicating with Jira.

"summary": "Field 'summary' cannot be set. It is not on the appropriate screen, or unknown." 

"description": "Field 'description' cannot be set. It is not on the appropriate screen, or unknown." 

"customfield_10152": "Field 'customfield_10152' cannot be set. It is not on the appropriate screen, or unknown." 

"assignee": "Field 'assignee' cannot be set. It is not on the appropriate screen, or unknown." 

Issue #1: The user creating a request gets an error

Issue #2: Multiple requests are created on the page. In two instances 4 requests were created, in another instance 5 were created

Issue #3: No Jira ticket is created

There have been minor changes, but nothing that I can think of that can cause this issue. The page was working fine for the last 2-3 months. Before that, once before the Jira tickets had stopped being created, but we thought that might be since the Epic had 100 Jira tickets under it. We created a new Epic and the Jira tickets started getting created. Not sure what the issue was then.

Currently using Confluence version 7.19.0 (GUI2.2022-10-27.10:16: 3d6ba409), if that helps.

[Alex Medved _ConfiForms_ · Accepted solution]

Hi

Most probably the user who wants to create a ticket in Jira (through ConfiForms) does not have permissions to do so.

These error message you see (from Jira) usually mean that (special "Jira" way of saying you dont have permissions)

Alex

[Satyajit Shukre]

Thank you, Alex, but it looks like the issue is still there. The person who created the page is no longer with the organization and I have been looking after it for the past few months. I see that the main change after which the problem appeared was that, in the Confiforms Form Definition, earlier showOnlyOwnRecords was true, and this was removed, after which the problem appeared.

But after reverting it, the problem still exists.

I also removed all references to an Atlassian crowd team that was present in some of the Confiforms blocks (visible only to the team or editable only by the team).

I am assuming the additonalFormAdmins and formSuperUsers do not matter as much? I tried removing and putting these back, but that did not help either.

[Alex Medved _ConfiForms_]

These settings have no effect on the permissions your user have in JIRA... 

Really nothing to do with those configuration parameters - it is all about the permissions in Jira project that this form is attempting to create issues in

This is what I was trying to say in my earlier comment and this is what you need to look at -> JIRA project

Alex

[Satyajit Shukre]

Ok, I understand now :)

I still need to know how to resolve this. So, every time a request is raised for Category 1 or Category 2 a JIRA story is created under Epic A or Epic B. Both of these are under JIRA project P.

Would you know if I can give watch permissions to all users to both these Epics A and B? Or is it possible to give permissions to the new stories under these? Or would I need to give view permissions to the Project P?

I will have to approach the JIRA admin who might not be keen to give permissions that are not needed. But it will be good for the people raising a request to see the JIRA stories for which they raise the request.

[Alex Medved _ConfiForms_]

I guess you need to look into Jira documentation on how to manage project permissions.

There is not much you can do (and should do) through ConfiForms

[Satyajit Shukre]

Thank you for the advice. I will check with the Jira admin and Jira documentation to see how to proceed.

Looks like I will have to inform the project team that using Confiforms to raise Jira tickets might create issues if there are people from other teams who might not have permissions to the relevant Jira boards and that this should be sorted out before allowing this functionality.

I will mark the question as solved, since it has shown the issue at hand was more of a Jira issue rather than a Confiform issue. Thank you.

[Alex Medved _ConfiForms_]

That's right - users must have permissions to create Jira tickets

Or you can switch to a WebService Request (IFTTT rule) in ConfiForms to be used with a dedicated service account instead - https://wiki.vertuna.com/display/CONFIFORMS/Configuring+ConfiForms+IFTTT+actions+and+rules#ConfiguringConfiFormsIFTTTactionsandrules-WebServiceRequest