-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jira Cloud initial setup fails - Custom field cannot be set. It is not on the appropriate screen, or unknown. #108
Comments
can you post the whole debug output? If that's non-ideal, then please email it to smcgrath at tenable.com |
Here it is:
Available IssueTypes11: Sub-task
3: Task
11222: Task
11210: Subtask
11208: Task
11220: Subtask
11218: Task
11224: Subtask /-------------------------------NOTICE-----------------------------------
|
Well there is the issue:
What you will likely need to do is get the screen IDs and hard-code them into your config. Follow the following instructions: To get the screen ids, you'll need to look in the URL path. In Jira's most recent UI, its at the end of the URL and looks like I really wish they would relay to the user what the IDs were in a more transparent way, sadly they do not. |
🤔 |
Did you create the project, or did the integration? |
I created it. That may be the issue. |
yeah, now Jira doesn't always play nice with re-used keys, you may need to add the key attribute to the jira stanza like so: jira:
key: VULNMNGT |
Fiddled aorund with the projects, got the integration doing all the job (creating a new project and customizing it). |
Running into a weird issue, where the initial Jira Cloud project's config fails.
It seems to be due to (recent?) changes in Jira Cloud UI.
Auth is good, Project/Key are good.
Below is the debug log extract using --troubleshoot option.
Have shortened it to where the Jira POST exception is raised, as everything prior is working like a charm.
I did try searching for the Jira Screen IDs but no luck.
Anybody else having this behaviour ?
Looks to me like Jira Cloud did again change their UI / API endpoints and the integration is not capable of dealing with it.
The text was updated successfully, but these errors were encountered: