My organization uses Issues to track top-level features (usually on support development) and then Subtasks to those Issues for individual requirements. An Issue might be "Linking not working as intended" with a subtask of "Write a new stored procedure to handle blanks."
For new development, you might check out the Agile module for JIRA. We have it, but I am not currently on the project that uses it.
An obvious solution is to use "Issue Type" to distinguish Bugs/Requirements.
Or maybe you could try adding a phony version "BACKLOG" where all requirements go first. Then put approved requirements into a planed sprint version (e.g. "R2011-S1"). This is a work-around when you do not have the Agile extension.
发布评论
评论（2）
我的组织使用问题来跟踪顶级功能（通常在支持开发上），然后使用这些问题的子任务来满足各个需求。问题可能是“链接未按预期工作”，其子任务为“编写新的存储过程来处理空白”。
对于新的开发，您可以查看 JIRA 的敏捷模块。我们有它，但我目前不在使用它的项目中。
My organization uses Issues to track top-level features (usually on support development) and then Subtasks to those Issues for individual requirements. An Issue might be "Linking not working as intended" with a subtask of "Write a new stored procedure to handle blanks."
For new development, you might check out the Agile module for JIRA. We have it, but I am not currently on the project that uses it.
一个明显的解决方案是使用“问题类型”来区分错误/需求。
或者，也许您可以尝试添加一个虚假版本“BACKLOG”，其中所有要求都放在第一位。然后将批准的需求放入计划的冲刺版本中（例如“R2011-S1”）。当您没有敏捷扩展时，这是一个解决方法。
An obvious solution is to use "Issue Type" to distinguish Bugs/Requirements.
Or maybe you could try adding a phony version "BACKLOG" where all requirements go first. Then put approved requirements into a planed sprint version (e.g. "R2011-S1"). This is a work-around when you do not have the Agile extension.