Hello Dataverse Community,
Starting this week, a group of us here on the Dataverse Team have begun to go through all of the open issues in the Dataverse software github repository. You might begin to see issues you have created change priority as well as a new priority labeling system start to be added to issues. Additionally, an effort label will be added to each issue.
How are we prioritizing issues? Our plan is to determine the Severity and Impact to User then multiply Severity x Impact to User to determine the Priority.
All four scales, Priority, Severity, Impact to User, and Effort, are included in this email to provide transparency on what the criteria is that we are using.
P4: Critical, consider to fix immediately (score of 25)
P3: Serious, consider to include in the next release (score of 15-20)
P2: Moderate, consider to schedule in the next two or three releases (score of 6-12)
P1: Low, schedule when time is available (score of 1-5)
S5: Data loss, data corruption, or system unavailable
S4: Important functionality is unavailable with no workaround
S3: Important functionality is unavailable but has a reasonable workaround
S2: Secondary functionality is unavailable but has a reasonable workaround
S1: Cosmetic issues or some functionality unavailable but has a simple workaround.
Impact to User Scale:
i5: Affects most or all users and/or a very large range of system functionality
i4: Affects a large set of users and/or large range of system functionality
i3: Affects a moderate set of users and/or moderate range of system functionality
i2: Affects a small set of users and/or a small range of system functionality
i1: Affects a minimal set of users and/or a very small range of system functionality
E5: Epic-Too big for one release
E4: Extra Large-Greater than a week
E3: Large-Within a week
E2: Medium-One to two days
E1: Small-Within a day
Please let us know if you have any questions.
Have a great weekend!
User Experience Lead
The Institute for Quantitative Social Science
Thanks for the nice words and questions! Since we are still in the beginning of using these scales and still navigating through the backlog of issues, we ask for authors to not include the severity, impact, and effort in issues they create. We will let the community know once we have used the scales enough and know they work well with all the Dataverse Github Issues (we’ve already had to adjust wording a few times). As in the past, authors who aren’t part of the Dataverse Development Team still aren’t able to add labels to issues and we aren’t sure yet if we will open up labels to the external community.