-
Notifications
You must be signed in to change notification settings - Fork 19
Closed
Labels
MVP Milestone 1MVP Milestone 1: The SetupMVP Milestone 1: The SetupSize: 10A percentage of a sprint. 7 hours.A percentage of a sprint. 7 hours.pm.GREI-d-1.7.1NIH, yr1, aim7, task1: Research & architecture for separating backend and frontendNIH, yr1, aim7, task1: Research & architecture for separating backend and frontend
Description
Overview of the Feature Request
The code repository does not have the appropriate tools and resources to properly categorize/tag the created issues, as well as issue templates to standardize its creation and structure.
These tools are necessary to be able to manage and visualize the evolution of the project, as well as the prioritization and monitoring of its issues in the backlog boards.
We can consider the existing tools of this nature that the Dataverse GitHub repository already has. (For example: I have already copied the sizing tags in this repository).
What kind of user is the feature intended for?
Dataverse developers and PMs
What inspired the request?
Creating first dataverse-frontend issue #1
What existing behavior do you want changed?
Repository management tooling
Any brand new behavior do you want to add to Dataverse Frontend?
New tags and issue templates, as well as any other helpful tool.
Any related open or closed issues to this feature request?
No
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
MVP Milestone 1MVP Milestone 1: The SetupMVP Milestone 1: The SetupSize: 10A percentage of a sprint. 7 hours.A percentage of a sprint. 7 hours.pm.GREI-d-1.7.1NIH, yr1, aim7, task1: Research & architecture for separating backend and frontendNIH, yr1, aim7, task1: Research & architecture for separating backend and frontend
Type
Projects
Status
No status