Label field not visible

[QA McCann]

Hi,

I'm in the process of trying to get Ranorex integrated with our instance of Jira Cloud and I get an error message that stops a ticket being created on test failure.

It's notifiying me that Labels isn't visible on the ticket type that is being created. However I'm 100% certain it's there (see screenshot).

Does anyone know if there any other permissions/settings for the Labels field that might not be obvious and would stop external software from creating a ticket?

The Label field isn't a custom field in this instance.

Thanks,

[Grigory Salnikov · Accepted solution]

Hello!

Could you please provide us with the actual error message?

Thanks in advance.

[QA McCann]

Yeah, sure thing. Here we go...

[Grigory Salnikov]

Ok, thank you!

Is it an "edit" or a "create" screen above?

If it's "create", I think you should also place the label field to the appropriate edit screen as recommended here:

Add Labels to Issue: Field 'labels' cannot be set. It is not on the appropriate screen, or unknown

[QA McCann]

Thanks Grigory!

The screenshot is from the create view, but the Labels field is also on edit.

I've seen some mention that it might be because I'm not the owner of the issue? Is owner the same as "assignee"? In which case, I can set myself to be the default assignee for these issues.

Or is owner a custom field that needs to be created?

[Grigory Salnikov]

I think we should also check Ranorex-user's permission. He should be able to create and edit tickets. What model do you use in the project permissions scheme? Is it a group- or a role-based model? Either way, please, make sure that the user has enough permissions to perform this operation.

Secondly, are you trying to actually set "Labels" field when creating a ticket? If you are not, maybe we should try and see what happens then.

Could you please also provide a Ranorex configuration that creates a Jira-ticket?

Thanks in advance.

P.S. And please, make sure once again, that the field is actually there, on the right screens. Sometimes it's easy to get lost in the configuration.

[Grigory Salnikov]

I've also done some search and came up with the following:

Exception — “ JIRA returned wrong status “

If you’re encountering an error like

‘{“errorMessages”:[], “errors”:{“summary”:”Field ‘summary’ cannot be set. It is not on the appropriate screen, or unknown.”, …}} ‘,

it is very likely that your Jira installation is customized in some way. This message tells, that the library wants to set a field, which is not available when performing the desired action. Please check your Jira installation and the respective action for all necessary and available fields. To overcome this issue, the underlying library needs to get extended and compiled by yourself. A potential starting point for modifications would be the JiraReporter class.

Though it's about the "Summary" field it might be relevant.

Btw., is your Jira instance customized in any way?

If I were you I'd try to do the same integration with another or fresh installation of Jira.

[QA McCann]

Hi Grigory,

Thanks for the reply on this and the effort to help out.

Ranorex suggested it may be the customization of our instance of JIRA so I will investigate with a new project and see if it still occurs.

Thanks,

[Grigory Salnikov]

Hi James,

You're welcome!

Have a nice week!

[QA McCann]

Hi,

So after a fair bit of trial and error I was able to find a situation in which I could get Ranorex to create a ticket in Jira.

It appears we had more customisation in our instance of Jira than I first realised!

I actually ended up creating a new ticket type called "Ranorex" for which I only had the fields that Ranorex requires on there. This worked and I saw no repetition of the error.

Quite why there was an issue with the Labels on a "Bug" issue type, I might never know but I'll report back if I find out.

Thanks for the help on this Grigory!

[Grigory Salnikov]

Hello @QA McCann!

You're always welcome!

I'm glad you've managed to overcome the issue.

Sometimes it takes a lot of effort and time to find a resolution. I had a situation when it took me a couple of months to resolve the problem.

Have a nice week!