How to express what do do when error occurs in a user story?
How do you express what to do when error occurs in a user story? Should the response to what happen on errors be in a task of the original user story, or should I create another user story that is concerned with what happens on errors?
How to express what do do when error occurs in a user story?
How do you express what to do when error occurs in a user story? Should the response to what happen on errors be in a task of the original user story, or should I create another user story that is concerned with what happens on errors?
How to express what do do when error occurs in a user story?
How do you express what to do when error occurs in a user story? Should the response to what happen on errors be in a task of the original user story, or should I create another user story that is concerned with what happens on errors?
How to express what do do when error occurs in a user story?
How do you express what to do when error occurs in a user story? Should the response to what happen on errors be in a task of the original user story, or should I create another user story that is concerned with what happens on errors?
How to express what do do when error occurs in a user story?
How do you express what to do when error occurs in a user story? Should the response to what happen on errors be in a task of the original user story, or should I create another user story that is concerned with what happens on errors?
Tracking internal builds versus public builds
At our office, we use JIRA to track issues reported by our QA teams. We also have Bamboo which builds each time we commit to our Git (Stash) repository. QA picks a build from Bamboo and they work with that build for about a week. Once all of the issues they filed on that build are resolved, they pick another build and regress/smoke test again until they find a fully passing build (i.e. no issues reported).
How to work on not User Story related tasks
I’d like to create a developer task collector where I’d put all issues that I see need some work but are not User Story related (e.g. fix some not visible quirks in startup animation, scan code with lint, enable EasyTracker in application, clean unused resources, etc.).
Scrum and backlogged issues
I run a development team that recently started using Jira and we began using agile scrum. I’m curious about a certain aspect of backlogged issues.
Scrum and backlogged issues
I run a development team that recently started using Jira and we began using agile scrum. I’m curious about a certain aspect of backlogged issues.