Jira Cloud integration : Predefined fields values are not synchronized with values from Jira

[amalbaccar-hub]

We have integrated our BTS plugin which is Atlassian Jira Cloud and Currently we have created 2 types of global integration for issue types bug internal & test case. The plugin version that was uploaded is 5.7.4 : https://github.com/reportportal/plugin-bts-jira-cloud/packages

When posting a new issue new values which are added in Jira cloud after plugin integration are not available for predefined fields. For example, we did not find all the Affected versions in the list of the affected version predefined field (version 2.0.3 not found, but it exist in our Jira cloud BTS):

Any help please @DzmitryHumianiuk @avarabyeu

[VolhaKarenko]

Hi @amalbaccar-hub, The latest Jira Cloud plugin version is 5.11.0, please download it here https://github.com/reportportal/plugin-bts-jira-cloud/packages/1366483 and check if the issue is still reproducible. Also please specify your ReportPortal version

[amalbaccar-hub]

Hi @VolhaKarenko , Thank you for your reply. Will try it and let you know. this is the version we are using:

[amalbaccar-hub]

@VolhaKarenko plugin was successfully installed :

However when clicking on button "Add integration" a blank page is shown:

I think this is due to version incompatibility (ReportPortal version 5.7.4 and plugin version 5.11.0).

[alena-babrova]

Hello @amalbaccar-hub,

You are absolutely right. Jira Cloud plugin version 5.11.0 is not compatible with your version of ReportPortal. Please, use Jira Cloud plugin version 5.7.3 for ReportPortal version 5.7.4. And close the ticket if it helps you.

[amalbaccar-hub]

Hello @alena-babrova,

Thank you for your reply. Any link to share please for version 5.7.3.

[alena-babrova]

Dear @amalbaccar-hub,

Please, find the plugin here

[amalbaccar-hub]

Thanks for sharing @alena-babrova

[amalbaccar-hub]

Hi again @alena-babrova @VolhaKarenko,

I tried both versions 5.7.2 & 5.7.3, however Unfortunately for both versions there is the issue of default properties not showing:

It seems this issue was fixed for version 5.7.4

[alena-babrova]

Dear @amalbaccar-hub,

Indeed, there is an issue in integration with the latest Jira Cloud. I have created a ticket in our internal system to fix it. I will inform you once it is fixed.

Thank you for reporting!

[amalbaccar-hub]

Thank you so much @alena-babrova please keep me updated.

Actually I noticed other problems (with plugin version 5.7.4):

• Bug priority gets changed. I posted a ticket with minor priority but it seems it gets created with blocker priority by default in Jira:

I think a similar issue was reported with older version. Found this thread: https://github.com/reportportal/reportportal/issues/1406

• Assignee field is unusable, values don't get automatically populated like other fields (Fix version for example) and when I put an existing Jira user it's not set in Jira ticket afterwards.
• We have a custom field named 'Parent' (which is supposed to point to Epic). Same behavior as Assignee field, I tried to put link to Epic or Epic ticket number but it's not working.

I think there is problem with custom fields in general so please try to resolve those issues as well.

Thanks again @alena-babrova

[amalbaccar-hub]

hello @alena-babrova any updates?

[alena-babrova]

Hello @amalbaccar-hub,

The issue related to the missing Jira Configuration fields is in progress in the current sprint. Once we have some results, I'll let you know.

By the way, as far as I see you've managed to configure the integration with Jira somehow https://github.com/reportportal/plugin-bts-jira-cloud/issues/69. How have you managed to do this if there were missing fields in the configuration? 🧐

[APiankouski]

Hi again @alena-babrova @VolhaKarenko,

I tried both versions 5.7.2 & 5.7.3, however Unfortunately for both versions there is the issue of default properties not showing:

It seems this issue was fixed for version 5.7.4

Hello @amalbaccar-hub do you use some custom field in jira? Is the field list empty for all issue types? Do you see any error message in /getIssueFields request in dev tools?

[APiankouski]

On same integration i found same bug in 5.7.2 version of plugin, but it work fine with latest 5.11.0 - download here

[amalbaccar-hub]

Hello @amalbaccar-hub,

The issue related to the missing Jira Configuration fields is in progress in the current sprint. Once we have some results, I'll let you know.

By the way, as far as I see you've managed to configure the integration with Jira somehow #22 (comment). How have you managed to do this if there were missing fields in the configuration? 🧐

Hello @alena-babrova,

Thank you for the update.

Actually using the plugin version 5.7.4 the integration is possible cuz the missing fields are optional. I was able to post issues from the beginning however there was a problem with some fields I mentioned in the previous comments.

[APiankouski]

Hello @amalbaccar-hub We are working on assigned and priority fields but we can't guarantee working of custom fields Hide fields in configuration if they cause the problems

[amalbaccar-hub]

Hi again @alena-babrova @VolhaKarenko, I tried both versions 5.7.2 & 5.7.3, however Unfortunately for both versions there is the issue of default properties not showing: It seems this issue was fixed for version 5.7.4

Hello @amalbaccar-hub do you use some custom field in jira? Is the field list empty for all issue types? Do you see any error message in /getIssueFields request in dev tools?

Hello @APiankouski ,

Thank you for your reply. Yes we are using many custom fields in Jira.

For "Parent" field which turns out to be a non custom field, the field list is empty (I checked for all issue types) and no error message for getIssueFields request:

Although we are having this values list in Jira:

Same thing for Assignee field:

[amalbaccar-hub]

Hello @amalbaccar-hub We are working on assigned and priority fields but we can't guarantee working of custom fields Hide fields in configuration if they cause the problems

Hello @APiankouski,

If you can also work on Parent field which is of type issuelink, it would be great. Otherwise we have to hide the fields with problems as you said.

Thanks!

[Kozovskaya]

Hello @amalbaccar-hub the issue with predefined fields values and Parent field is fixed and will be available with our next product release when the plugin will also be updated. The issue with Assignee is not fixed yet and I'm not sure that we will have time to fix it prior next release. I'll keep you informed!

[amalbaccar-hub]

Hello @Kozovskaya

Sounds good! Thank you so much for the update.

[APiankouski]

Previously, the Assigned To field worked with the username, but it is deprecated in Jira Cloud As a quick fix, the Assigned To field will work with the account ID in the next release We understand that this is not always convenient to use, so we are planning to implement search as in Jira (by name, email)

[amalbaccar-hub]

@APiankouski Okay I see thanks for the explanation.

[VeranikaRymzha]

Hello @amalbaccar-hub, The issue with the 'Assignee' field has been resolved. The 'Assignee' field now works by using the assignee's name (RP provides suggestions) and email (in case of an exact match).

These changes have been released as a part of ReportPortal version 24.2 + new Jira Cloud plugin.

You can find more details about the new features and enhancements in the release notes. Feel free to try it out and share any feedback you may have.

Have a great day!

[DzmitryHumianiuk]

@VeranikaRymzha @amalbaccar-hub can we consider the ticket closed now?

[VeranikaRymzha]

@DzmitryHumianiuk , no, the issue is resolved for 'Assignee' field only.