allure-framework / allure-framework/allure2
@Story should be linkable as issue and tms
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
**Is your feature request related to a problem? Please describe.**
Right now, we have:
```
allure.link.issue.pattern=https://[JIRA]/browse/{}
allure.link.tms.pattern=https://[TESTRAIL]/index.php?/cases/view/{}
```
And this allow us to link from the report to these external tools. We are missing some extra options.
**Describe the solution you'd like**
Most of our test cases have these annotations:
```
@Test
@Story("JIRA-ID")
@TmsLink("TR-ID")
```
@Story is working fine for mapping behaviors, but in the report, we would like to have a link to the story in JIRA, in the same way we have when we use @issue annotation.
**Describe alternatives you've considered**
Of course, we could use @issue to link stories, but then we would lose the behaviors. And we would be mixing different concepts: issues (bugs) vs stories
Contributor guide
Research direction
Start by tracing how @Story and @TmsLink metadata is handled in the report, alongside the existing allure.link.issue.pattern and allure.link.tms.pattern settings. Confirm that stories remain available for behavior mapping while also becoming links to the configured external tools; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100