I am facing a strange issue. When I try mark a Sprint complete (that has some incomplete tasks, which should spill over to next Sprint), I get a message that the Sprint cannot be marked complete because two Stories (the story key is also displayed) have incomplete sub-tasks. The strange thing is that both these stories do not even belong to this Sprint and have been marked with the upcoming sprint.
Another Strange thing:
The two parent Stories and the sub-tasks with in them are in "TO DO" state, and the Sprint field for them show the Next Sprint, the sub-tasks inherit the field value from their parent. We use the "next-gen" JIRA and use the standard workflow.
Definitely whenever you want to track the status of an entity (be it real world like a device or something abstract like a requirement or a bug) JIRA is a good candidate to enter the play.
Besides what you mentionned I like to get automated reminders from subscriptions, e.g. for overdue issues or weekly reports ai have to do. Excel can't do that for you, it's passive until you open it. Using customized mail templates you can automatically provide reports for managers as soon as critical actions have been taken, e.g. when an expensive equipment breaks.
The problems you will probably face with JIRA is to get acceptance for the user interface by end users (not developers). But since there is SpeakEasy you can also better customize the UI for more unexperienced users and hide away a lot of all the bells and whistles in JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.