Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
Rephrasing my previous question -
Project Scenario - Sprint 5 is for complete system Integration testing then Sprint 6 is for bug fix for a developer to fix issues which were logged in Sprint 5. Sprint 7 is assigned for Bug verification and retesting along with any new fixes and bug closure.
Bugs are logged in Sprint 5 under the task 'Test case execution' and tagged with sprint 5. When such bugs are available for retesting in Sprint 7 then bug can be closed without changing sprint number in JIRA. But which task needs to be created in Sprint 7 for a tester? and is there any change require in sprint number against bug.
Product Scenario - Version 1.0 is released and bugs logged. Few bugs resolved , fixed and closed. Few bugs were deferred and fixed in next release.
How to manage in JIRA sprints these scenarios? Kindly guide.
It sounds like you're misusing sprints to be honest. Sprint 5 sounds fine for logging the integration test items, but you don't know how many things are going to come out of it or if you'll have time to fix them in sprint 6. So you should let people log issues arising and then plan sprint 6 when you've got enough to fill it. Sprint 7 sounds wrong - if you need to verify that bugs are being fixed, build it into the workflow.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
As a Jira power user, I was at first doubtful that Trello could benefit my workflow. Jira already uses boards (ones you can customize!), so why would I even need to use Trello?! In this post you will...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs