-
Suggestion
-
Resolution: Fixed
-
None
-
None
- Same defaults when choosing the sprint as in
GHS-6467 - Needs to take non-working days into account (we should make it explicit in the description of the gadget)
- Mimic behaviour of classic version of the gadget otherwise
- Wallboard compatible
- Call it "Days Remaining in Sprint" gadget
Development Notes
Q: What happens if a user doesn't have permission to access a project in the gadget?
A: 
No permission error message?
Q: Will the days remaining be calculated in the server timezone or adjusted to user timezone? (I think it would have to follow the server timezone to be accurate for remote teams)
A: User's timezone
Q: Do the days remaining honor the time of day that the sprint ends?
A: Yes
Q: What is displayed if there is no active sprint?
A: No active sprint error message
Q: What is displayed if the sprint has been closed?
A: 0 Days Remaining
- is related to
-
- Closed
-
- Closed
- relates to
-
- Closed
1.
|
Only scrum boards should be selectable |
|
Closed | Unassigned |
2.
|
only sprints which aren't complete should be selectable |
|
Closed | Unassigned |
3.
|
Weird rendering of a red 0 before the actual number |
|
Closed | Unassigned |
4.
|
I change the user timezone, yet the days remaining stayed the same |
|
Closed | Unassigned |
5.
|
wallboardification |
|
Closed | Unassigned |
6.
|
Non working days not taken into account |
|
Closed | Unassigned |
7.
|
align messages with burndown gadget - warning instead of error |
|
Closed | Unassigned |
8.
|
Sprint is shown even if complete |
|
Closed | Unassigned |
9.
|
Days remaining long words may be trouble - add the following css |
|
Closed | Unassigned |
[JSWCLOUD-6466] As a product owner, I'd like a days remaining in sprint gadget for the new boards (similar to the days remaining gadget)
on GHS-6466-days-remaining-gadget
Uses user/server timezone and is calculating a calendar days till the end of sprint.
George Carvill
added a comment - My opinions:
Q: What happens if a user doesn't have permission to access a project in the gadget?
A: In place of the gadget display would me an appropriate message, e.g. "Unavailable. Please contact your JIRA System Manager."
Q: Will the days remaining be calculated in the server timezone or adjusted to user timezone? (I think it would have to follow the server timezone to be accurate for remote teams)
A: I don't think I care where the days remaining are calculated so long as the result is displayed in the user's timezone.
Q: Do the days remaining honor the time of day that the sprint ends?
A: No opinion
Q: What is displayed if there is no active sprint?
A: An appropriate message, such as "Please select an active sprint."
Q: What is displayed if the sprint has been closed?
A: No opinion
George Carvill
added a comment - My opinions:
Q: What happens if a user doesn't have permission to access a project in the gadget?
A: In place of the gadget display would me an appropriate message, e.g. "Unavailable. Please contact your JIRA System Manager."
Q: Will the days remaining be calculated in the server timezone or adjusted to user timezone? (I think it would have to follow the server timezone to be accurate for remote teams)
A: I don't think I care where the days remaining are calculated so long as the result is displayed in the user's timezone.
Q: Do the days remaining honor the time of day that the sprint ends?
A: No opinion
Q: What is displayed if there is no active sprint?
A: An appropriate message, such as "Please select an active sprint."
Q: What is displayed if the sprint has been closed?
A: No opinion George Carvill
added a comment - A - 12 months to re-deliver a feature that disappeared in an upgrade seems a little inadequate.
B - I like the idea of an open approach to your backlog ordering. How to I see the prioritized list?
George Carvill
added a comment - A - 12 months to re-deliver a feature that disappeared in an upgrade seems a little inadequate.
B - I like the idea of an open approach to your backlog ordering. How to I see the prioritized list? Hi Everyone,
Thanks so much for your votes and comments on this feature request, we wanted to provide an update on the status.
We know there are features missing from the new Scrum and Kanban boards. We currently plan to deliver a gadget for the days remaining within the next 12 months.
Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you!
Thanks for your patience, we hope that our open approach to feature requests and backlog ordering allows you to see where we are headed.
Cheers,
Shaun Clowes
GreenHopper Product Manager
Hi all,
Many thanks for your feedback on this issue. This has now been implemented and is shipping with GreenHopper 6.1.6.
Regards
Tom Kotecki
Product Manager, GreenHopper