agile-gitlabce issueshttps://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues2020-04-14T10:32:48-04:00https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/39Remove chart estimate2020-04-14T10:32:48-04:00Lily RomanoRemove chart estimate## User story
As a [new users]
I want [only one chart option]
So that [I'm not confused]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ]
## Acceptance criter...## User story
As a [new users]
I want [only one chart option]
So that [I'm not confused]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ]
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ]
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/38Assign multiple team members2019-12-15T13:45:21-05:00Lily RomanoAssign multiple team members## User story
As a [Scrum Master]
I want [to assign multiple team members to an issue]
So that [reporting is more accurate and users know what they need to do]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to ...## User story
As a [Scrum Master]
I want [to assign multiple team members to an issue]
So that [reporting is more accurate and users know what they need to do]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- To adhere to Gitlab CE limitations
- [ ] Select Primary assignee (mark as the assignee on Gitlab)
- [ ] Select Secondary assignee(s) (mark as comment with @ tag in description)
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can assign multiple users to an issue.
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/32Toggle today marker on Burndown chart2019-12-15T12:43:34-05:00Lily RomanoToggle today marker on Burndown chart## User story
As a []
I want []
So that []
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ]
## Acceptance criteria
<!--- What is required for the story to be ...## User story
As a []
I want []
So that []
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ]
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ]
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/36Represent Spikes2019-12-15T12:43:14-05:00Lily RomanoRepresent Spikes## User story
As a [Scrum Master]
I want [Manage Spikes]
So that [I can track time spent not specifically on writing code]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - ...## User story
As a [Scrum Master]
I want [Manage Spikes]
So that [I can track time spent not specifically on writing code]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] https://www.visual-paradigm.com/scrum/what-is-scrum-spike/
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ]
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/37Represent School Breaks2019-12-15T12:42:53-05:00Lily RomanoRepresent School Breaks## User story
As a [Scrum Master]
I want [a way to including long school breaks such as Thanksgiving and Sprint Break]
So that [I can better understand the flow of work]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change...## User story
As a [Scrum Master]
I want [a way to including long school breaks such as Thanksgiving and Sprint Break]
So that [I can better understand the flow of work]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- Research:
- [ ] Continue the burndown of ideal or maintain?
- [ ] How to indicate on chart
- [ ] What other features does this impact?
- [ ] Implement
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can indicate when the school has a break so that I can better understand my burndown chart and work assignments
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/35Refine OAuth flow2019-12-10T13:56:09-05:00Lily RomanoRefine OAuth flow## User story
As a [User]
I want [a seamless login experience]
So that [I can use the website with confidence]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [Au...## User story
As a [User]
I want [a seamless login experience]
So that [I can use the website with confidence]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [Auth0 Single Page App SDK](https://auth0.com/docs/libraries/auth0-spa-js)
- [ ] Log in updated
- [ ] API Calls updated
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] Log in is seamless
- [ ] API Calls are seamless
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/27Display table of which issues have issues2019-12-03T20:44:22-05:00Lily RomanoDisplay table of which issues have issues## User story
As a [developer]
I want [see what issues need some attention re: estimate.spemd]
So that [I can keep an accurate accounting]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to ...## User story
As a [developer]
I want [see what issues need some attention re: estimate.spemd]
So that [I can keep an accurate accounting]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- Report the following
- [x] Issues with spend and no estimate
- [x] Issues with spend > estimate (report differently than the previous line)
- Milestones with issues that have spend outside of the milestone range
- [ ] Report issues
- Allow ignoring a specific spend (use API to leave a commented out line in the description in Gitlab to ignore the spend)
- [ ] Add comment to Gitlab
- [ ] Search for comment and ignore when reporting
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] All identified issue issues are reported.
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/29Organize Sprints into Releases2019-12-03T20:41:11-05:00Lily RomanoOrganize Sprints into Releases## User story
As a [Scrum Master]
I want [see a burndown over several sprints]
So that [I can see the progress of a release]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- ...## User story
As a [Scrum Master]
I want [see a burndown over several sprints]
So that [I can see the progress of a release]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Wireframe solution
- [ ] Break into tasks
- [ ] Complete
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can view burndown by sprint, release, all issues, or unattached issues
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/33Second Axis for Completed Hours2019-12-03T20:40:32-05:00Lily RomanoSecond Axis for Completed Hours## User story
As a [Scrum Master of a large project]
I want [to see completed hours per day regardless of the y-axis scale]
So that [I can see trends in work being done]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change...## User story
As a [Scrum Master of a large project]
I want [to see completed hours per day regardless of the y-axis scale]
So that [I can see trends in work being done]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Determine at what point should the completed hours slip to it's own axis.
- [ ] Implement the changes
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can see completed hours and the bars are visible.
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/34By Completed Tasks as well as by spent hours2019-12-03T20:40:24-05:00Lily RomanoBy Completed Tasks as well as by spent hours## User story
As a [Scrum Master]
I want [to view burndown by task effort]
So that [I can see how quickly boxes are being checked off]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link...## User story
As a [Scrum Master]
I want [to view burndown by task effort]
So that [I can see how quickly boxes are being checked off]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] % of tasks completed `- [ ]` vs `- [x]`
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can switch between chart types
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/9Add new Gitlab OAuth workflows2019-11-12T07:22:00-05:00Lily RomanoAdd new Gitlab OAuth workflows## User story
As a [user of a Gitlab site not already set up to use the OAuth flow]
I want [to add my site as being able to utilize the OAuth flow]
So that [I don't need to use an API Key anymore]
## Tasks
<!-- Add as many bullet...## User story
As a [user of a Gitlab site not already set up to use the OAuth flow]
I want [to add my site as being able to utilize the OAuth flow]
So that [I don't need to use an API Key anymore]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [x] Restructure the code to make a simple location that can be easily updated by a code novice for updating the site dropdown
- [ ] Provide a link to feedback for other local GitHub installs to be available via the OAuth authentication workflow
- [ ] Provide instructions on how to update the repository and submit a PR to have a new site added
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can request to have my Gitlab install added
- [ ] I can create a PR to write the code myself to have Gitlab added
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/5How to "fix" hours instruction page2019-11-12T07:21:41-05:00Lily RomanoHow to "fix" hours instruction page## User story
As a [team member]
I want [to have a single, easy reference on Gitlab time commands]
So that [I can fix my input mistakes]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to li...## User story
As a [team member]
I want [to have a single, easy reference on Gitlab time commands]
So that [I can fix my input mistakes]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [x] Create a new nav-tab for instructions (logged in)
- [ ] Write up the instructions
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] Fix hour instructions added
## Notes
<!--- Why How --->
Temporary (shorter) resolution for issue #6.https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/6Time Spent management within app2019-11-12T07:19:45-05:00Lily RomanoTime Spent management within app## User story
As a [team member]
I want [be able to update the time spent from this page]
So that [I don't have to keep going back and forth]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers ...## User story
As a [team member]
I want [be able to update the time spent from this page]
So that [I don't have to keep going back and forth]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Display table of issues by sprint
- [ ] Allow displaying time detail of each each
- [ ] Match up any + and - spent hours on a single day (how to display?)
- [ ] Provide the ability to add or subtract time as necessary
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can add hours spent to an issue
- [ ] I can remove hours spent to an issue
## Notes
<!--- Why How --->
Longer to implement resolution for issue #5. If this issue is completed prior to #5, be sure to close #5.https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/10Filter Issue Table2019-11-12T07:19:39-05:00Lily RomanoFilter Issue Table## User story
As a [scrum master]
I want [to be able to filter the issues table]
So that [can better see what is going on]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - ...## User story
As a [scrum master]
I want [to be able to filter the issues table]
So that [can better see what is going on]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Filter on state and milestone
- [ ] Display filtered issue lists on Burndown tab filtered by milestone
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can filter by state
- [ ] I can filter by milestone
- [ ] I can see filtered by milestone list on the burndown tab
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/12Move logout button2019-11-12T07:19:35-05:00Lily RomanoMove logout button## User story
As a [user]
I want [to log out from the API login]
So that [I can restart as OAuth]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Move the log...## User story
As a [user]
I want [to log out from the API login]
So that [I can restart as OAuth]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Move the logout button to the outside of the appropriate div
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can see Log out on the OAuth screen
- [ ] I can see Log out on the API screen
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/14GitHub corner2019-11-12T07:19:24-05:00Lily RomanoGitHub corner## User story
As a [developer]
I want [a better indicator link to the repo]
So that [see under the hood]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] [Add ...## User story
As a [developer]
I want [a better indicator link to the repo]
So that [see under the hood]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] [Add corner](https://github.com/tholman/github-corners)
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] I can click thru to repo
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/18Research what start/end date to use on the "other" milestones2019-11-12T07:19:01-05:00Lily RomanoResearch what start/end date to use on the "other" milestones## User story
As a [user]
I want [a start and end date that makes sense on all possible options in the Milestone dropdown]
So that [my charts make sense]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the is...## User story
As a [user]
I want [a start and end date that makes sense on all possible options in the Milestone dropdown]
So that [my charts make sense]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Research the best way to display for offical milestones
- [ ] Research the best way to display for the "All issues" and "no milestone issues"
![image](/uploads/328ffc74cfbdc1f1a630a9d222532c9e/image.png)
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] All start and end dates make sense all burndown charts.
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/19Update input fields2019-11-12T07:18:55-05:00Lily RomanoUpdate input fields## User story
As a [user]
I want [a clean input experience]
So that [I enjoy using the website]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Update the Git...## User story
As a [user]
I want [a clean input experience]
So that [I enjoy using the website]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Update the Gitlab URL field
- [ ] Update the API Key field
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] Input fields are visually appealing
## Notes
<!--- Why How --->
[Bootstrap Option](https://getbootstrap.com/docs/4.1/components/input-group/)https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/20Explore adding Github2019-11-12T07:18:52-05:00Lily RomanoExplore adding Github## User story
As a [user]
I want [to use the website regardless of Github or Gitlab]
So that [I can use a tool I'm familiar with regardless of the project]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the ...## User story
As a [user]
I want [to use the website regardless of Github or Gitlab]
So that [I can use a tool I'm familiar with regardless of the project]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Expore the idea
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] Accept or reject the idea
## Notes
<!--- Why How --->https://gitlab.bucknell.edu/nrr004/agile-gitlabce/-/issues/22Link User Stories and Tasks2019-11-12T07:18:48-05:00Lily RomanoLink User Stories and Tasks## User story
As a [scrum master (advanced)]
I want [maintain tasks separate from issues]
So that [I can drill the work down further per sprint]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbe...## User story
As a [scrum master (advanced)]
I want [maintain tasks separate from issues]
So that [I can drill the work down further per sprint]
## Tasks
<!-- Add as many bullets as needed -->
<!-- Change the X to the issue numbers to link -->
<!-- - #X -->
- [ ] Research some ways to handle
- [ ] Breakdown into smaller tasks
## Acceptance criteria
<!--- What is required for the story to be completed -->
- [ ] See a "burndown" per user story
## Notes
<!--- Why How --->