Skip to content
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

"Appropriate screen, or unknown" error #67

Closed
Clickbaitcake opened this issue Sep 2, 2020 · 6 comments
Closed

"Appropriate screen, or unknown" error #67

Clickbaitcake opened this issue Sep 2, 2020 · 6 comments

Comments

@Clickbaitcake
Copy link

Clickbaitcake commented Sep 2, 2020

When running the integration from Tenable.io to Jira cloud I get the following error. Am stuck on how to fix or workaround other than completely deleting the project and its internals.

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

From the script log (In warn mode)
2020-09-02 11:17:06,990 restfly.errors.BadRequestError ERROR [400: POST] https://ABC.atlassian.net/rest/api/3/issue?update_history=False body$

Is this an issue with the integration not mapping fields correctly similar to the other common problems listed on the Read Me?

@SteveMcGrath
Copy link
Collaborator

can you please submit the output of a --troubleshoot run?

@shaygrantt
Copy link

tenable_debug_old.log

please see attach I am having the same issue.

@SteveMcGrath
Copy link
Collaborator

@kidshay your issue appears to be one of a screen selection issue. Refer to #23 (comment)

@Clickbaitcake
Copy link
Author

Hello @SteveMcGrath

When I run: tenable-jira config.yaml --troubleshoot I get back: Error: no such option: --troubleshoot
What am I doing wrong?

Thank you!

@SteveMcGrath
Copy link
Collaborator

@Clickbaitcake what version are you running?

@SteveMcGrath
Copy link
Collaborator

Closing per request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants