Prevent imported feature files from changing existing issue data

[csvtuda]

When importing feature files during feature file synchronization, any existing issue information is replaced with the imported feature file's data (summaries, steps, tags, ...). Having an option at hand for disabling this behaviour would be useful.

The jira ticket title is altered too, although I just wanted to upload the Feature with the background steps together. So either I dont upload anything or my tickets are altered completely (title, tags, cucumber steps), but I wished only the steps to be uploaded or altered.

Originally posted by @alexviz7 in #86 (comment)

[csvtuda]

Related to #83.

[csvtuda]

Hey @alexviz7, I just released version 4.0.0, which now automatically backups the issues' summaries. Should the imported feature file change them, they will be reset afterwards. Can you check if this works for you? If it does, I will add more backup options (description, labels).

[alexviz7]

The title isn't changed, but labels are still altered with option uploadFeatures: true, and uploadResults: true.

[csvtuda]

Ok thank you for confirming, I will add label backups and description backups then in the next few days.
I mostly only have access to a cloud instance and was unsure if this approach of reverting import changes works for server instances too. I will ping you again once it's done.

[alexviz7]

Also test execution files now have as an assignee the standard assignee of the project, which is the product owner, but not the one with the Jira PAT, which is me. This was not the case with the previous version.

[csvtuda]

Just to clarify: does this apply to:

• existing test execution issues which are modified by the plugin
• new test execution issues created by the plugin
• both?

I should probably add an option to assign created test execution issues to specific users.

[alexviz7]

Creating any jira ticket manually will have the assignee input field filled with the name of the product owner, so Its not an issue perse. However with the previous plugin versions the ticket created by the plugin had my name as an assignee as it was my PAT that was used.

[alexviz7]

issue with labels and assignee is still reproducible with the version 4.0.1

[alexviz7]

Creating any jira ticket manually will have the assignee input field filled with the name of the product owner, so Its not an issue perse. However with the previous plugin versions the ticket created by the plugin had my name as an assignee as it was my PAT that was used.

I think it is a minor issue since I will use fixed test execution files instead of generating new ones each time.

[alexviz7]

@csvtuda
Hi how is the progress going?

[csvtuda]

I'm working on it, but life has been busy. It's taking a little bit longer because I need to introduce new options, and I'm careful around new options to prevent a series of breaking bug fix changes.

[csvtuda]

Hey @alexviz7,

Version 4.0.2 is now released and should include a fix which resets the labels to their original set after a successful feature file import.

The new version does not include any updates to your assignee problem, though.

Can you confirm if the label reset works?

[alexviz7]

Hi i ve just tried it. Without the JIRA_TEST_EXECUTION_ISSUE_KEY="PRJ=1234" in the command line it works fine.
With it in the command line I have the following error:

│ Cypress Xray Plugin │ INFO │ Uploading Cucumber test results...
An error was thrown in your plugins file while executing the handler for the after:run event.

The error we received was:

TypeError: result.tags is not iterable
at C:\Projects\node_modules\cypress-xray-plugin\src\conversion\importExecutionCucumberMultipart\importExecutionCucumberMultipartConverter.js:20:63
at Array.forEach ()
at ImportExecutionCucumberMultipartConverterServer.convert (C:\Projects\node_modules\cypress-xray-plugin\src\conversion\importExecutionCucumberMultipart\importExecutionCucumberMultipartConverter.js:10:15)
at uploadCucumberResults (C:\Projects\node_modules\cypress-xray-plugin\src\hooks.js:254:170)
at afterRunHook (C:\Projects\node_modules\cypress-xray-plugin\src\hooks.js:193:40)
at C:\Projects\node_modules\cypress-xray-plugin\src\plugin.js:32:40
at Object.handler (C:\Projects\node_modules\cypress-on-fix\index.js:32:29)

As I do not want to generate a new test execution ticket each time, which will also have the standard assignee, I would prefer to use a fixed execution ticket for my test runs.

[csvtuda]

Hey @alexviz7,

version 4.0.3 should fix the error.

[alexviz7]

I run various tests with or without test execution ticket and I couldn't find a bug anymore. It works Thank you! Ticket can be closed.