Refactor of Jira Export Plugin

[SeleniumTestAB]

Context

Sending a Pull request do refactor Jira Export Plugin. Its more detailed one from my previous PR and now the plugin should work.

Checklist

• Sign Allure CLA
• Provide unit tests

[damonpam]

Hello! when this merge will be released? thanks!

[spursbob]

Hello! when this merge will be released? thanks!

Ditto that. I am getting error "[JiraExportResult(issueKey=AL-23, externalId=null, status=failed, message=externalId should not be empty)]" and wondering if related to this fix.

[SeleniumTestAB]

@spursbob are you using Jenkins or some kind of CI server that marks itself as executor? Because the executors build number is taken for externalId (since there was no better parameter to set there from allure).

[spursbob]

I figured things out eventually. I was copying an executor.json file in to a local Allure folder each time before generating the report but I guess I had forgotten to in this instance. The other issue I had, if I recall, was having the old Allure Pytest plugin installed along with the new one. Once I got it working I was happy, I think it is pretty awesome. I wish there was an option to not add the result if the Jira issue is Done or Closed but perhaps I can script that. Otherwise it could be updating issues for years. Thanks for your reply.

…

On Sun, 28 Jun 2020, 11:03 am SeleniumTestAB, ***@***.***> wrote: @spursbob <https://github.com/spursbob> are you using Jenkins or some kind of CI server that marks itself as executor? Because the executors build number is taken for externalId (since there was no better parameter to set there from allure). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1086 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKTBV3AN3WRSVEBI2BQ5AXDRY5ERTANCNFSM4MXGZV6Q> .