Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Two errors from the same commit:
✖ features/cart/coupon.feature:9 tags/jira @jira:demo12 must look like PROJ-123.
✖ features/cart/coupon.feature:20 tags/github @github:abc must be an issue number.I get that the second one wants a number. What is wrong with demo12? Our board key really is lowercase in the URL.
Accepted answer
The lowercase is the problem, and so is the missing dash. @jira: wants the canonical issue key shape: an uppercase letter, then more uppercase letters or digits, then a dash, then digits. DEMO-12 passes. demo12, DEMO12 and demo-12 all fail.
Jira itself renders keys uppercase and its URLs are case-insensitive, so the one you see in the address bar is not evidence. Take the key from the issue header.
@github: is stricter still — digits only, no #, no owner/repo prefix:
@ui @regression @jira:DEMO-12 @github:412
Scenario: A coupon below the minimum spend is rejectedBoth tags exist so the run viewer can link the scenario back to the issue, which is why the shape has to be exact rather than nearly right.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.