Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify the Stanford Email Use Case #109

Open
curtislisle opened this issue May 6, 2021 · 0 comments
Open

Clarify the Stanford Email Use Case #109

curtislisle opened this issue May 6, 2021 · 0 comments
Assignees
@curtislisle
Projects
Sprint Board (4 week)
Milestone
MIQA ticketing sy...

Comments

@curtislisle
Copy link
Collaborator

Stanford is currently using email to coordinate betwee reviewers. They have said they would like it if MIQA has capability like a ticketing system. However, their desires and reqirements are not well defined. This task is to work with Stanford to better understand and and docuent their use case.
@curtislisle curtislisle self-assigned this May 6, 2021
@curtislisle curtislisle added this to Triage (Needs Grooming) in Sprint Board (4 week) via automation May 6, 2021
@curtislisle curtislisle moved this from Triage (Needs Grooming) to Ready (Priority) in Sprint Board (4 week) May 6, 2021
@curtislisle curtislisle moved this from Ready (Priority) to In Progress in Sprint Board (4 week) May 6, 2021
@aashish24 aashish24 moved this from In Progress to Ready (Priority) in Sprint Board (4 week) May 10, 2021
@aashish24 aashish24 added this to the MIQA ticketing system milestone May 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@curtislisle curtislisle

Labels
None yet
Projects
Sprint Board (4 week)
  
Ready (Priority)
Milestone
MIQA ticketing system
Development

No branches or pull requests
2 participants
@aashish24 @curtislisle