You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several projects in the JIRA I connect to and there is only one project which I have an access to.
When I've tried to use the extension to create a new ticket it failed with an exception "Request failed with status code 400".
After a short research I found out that the problem is that the extension tries to get data about allowed issue types for the project which I don't have an access to: rest/api/2/issue/createmeta/<project_id>/issuetypes
As far as I understand, the extension tries to get data about all the projects in the JIRA and their allowed issue types when ticket creation command is called in order to display correct ticket creation panel.
I've tried to set up 'atlascode.jira.workingProject' property with the id of my project, but it doesn't help.
Is there any way to restrict the list of projects in the JIRA for ticket creation command?
The text was updated successfully, but these errors were encountered:
There are several projects in the JIRA I connect to and there is only one project which I have an access to.
When I've tried to use the extension to create a new ticket it failed with an exception "Request failed with status code 400".
After a short research I found out that the problem is that the extension tries to get data about allowed issue types for the project which I don't have an access to: rest/api/2/issue/createmeta/<project_id>/issuetypes
As far as I understand, the extension tries to get data about all the projects in the JIRA and their allowed issue types when ticket creation command is called in order to display correct ticket creation panel.
I've tried to set up 'atlascode.jira.workingProject' property with the id of my project, but it doesn't help.
Is there any way to restrict the list of projects in the JIRA for ticket creation command?
The text was updated successfully, but these errors were encountered: