We have been using trello for three years and we love how light weight it is, we create user stories and then we create technical tickets.
What is the best practice for linking technical tickets to a user story, so we know when the user story is done.
I know we can link to a trello ticket in the description/comments, but is this the best way? It still seems that I have to do a lot of matching up to see when tickets have been moved to done. I have tried using labels too - but similar overhead.
Is there a best practice way to do this?
I've seen people suggest checklists. You can use the url to another card in the checklist item name, as it will create a linked card.
Other people keep the technical tasks on a different board and use labels as the relation marker.
However you do it, is important to keep in mind that the great thing about Trello is the freedom. You'll never be constrained to a best practice of a standard, unless you impose it yourself.
I usually replicate the JIRA workflow on my boards:
Labels:Epic > Lists:Workflow > Cards:Stories and Tasks
Like I said, an idea to keep the clutter down would be to segregate the technical tasks to other boards and link them in your main board. A tool like Butler could help with maintenance and automation of links.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A blank Trello board can be both a beautiful and intimidating thing. How many lists should I have? Is creating 10 labels overkill? How can I best track my progress? Is there a way...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG