Page History

...

Each .feature file will be processed as follows.

Tests:

1. try to find the Test by key (in that project), if found then update it; else...
2. try to find the Test having both
   1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
   2. a label named "id:xxx", where xxx is some number (e.g. "id:1", "id:32"); this label comes from a scenario/scenario outline's tag
3. try to find the Test having both
   1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
   2. the same summary
4. try to find the Test by summary (in that project), if found then update it; else...
5. create Test in that project and add a label with the relative path of the feature, and another label corresponding to a tag "id:xxx" (if it exists)

Pre-Conditions:

1. try to find the Pre-Condition by key (in that project), if found then update it; else...
2. try to find the Pre-Condition having both
   1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
3. try to find the Pre-Condition by summary (in that project), if found then update it; else...
4. create Pre-Condition in that

...

1. project and add a label with the relative path of the feature

The mapping from the Scenario/Scenario Outline present in the .feature files to the Test issues in Jira would be as follows:

...