Timeline for Jira Ticket best practices
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 3, 2020 at 22:59 | history | suggested | Nic |
add tag: jira
|
|
| Mar 3, 2020 at 18:19 | review | Suggested edits | |||
| S Mar 3, 2020 at 22:59 | |||||
| Mar 3, 2020 at 5:02 | vote | accept | Cornelis de Jager | ||
| Mar 2, 2020 at 8:31 | history | edited | Ashok Ramachandran |
edited tags
|
|
| Mar 2, 2020 at 4:52 | answer | added | Ashok Ramachandran | timeline score: 2 | |
| Mar 2, 2020 at 0:04 | history | edited | Cornelis de Jager |
edited tags
|
|
| Feb 29, 2020 at 15:47 | comment | added | Vicki Laidler | Hi Cornelis - you've framed and tagged this as a question about Jira, but it sounds like you are asking a question about ticket best practices that is actually tool-agnostic. If you frame and tag it more generally, you might get more responses. | |
| Feb 27, 2020 at 13:01 | comment | added | Baracus | Defined standard? Not that I have seen. But one line tickets are an obvious no-no. A principle I work from is that anyone in the delivery team (product owner/developer/tester/ba etc.) should be able to understand the ticket and do the work that they need to do accurately from it. How do you test a one liner that says "fix login process"? | |
| Feb 26, 2020 at 22:10 | review | First posts | |||
| Feb 26, 2020 at 22:23 | |||||
| Feb 26, 2020 at 22:08 | history | asked | Cornelis de Jager | CC BY-SA 4.0 |