2024-04-02 Meeting notes

Apr 2, 2024

11:30am-1pm ET

Zoom link

 Participants

  • @Matthew Neely

  • @Matt Strauss

  • @Keli Schmid

  • @Tom Steele - regrets

  • @Alexander Duryee

  • @Christine Di Bella

  • @Mattie Clear

  • @Brianna McLaughlin

  • @Donald Smith

  • @Dillon Thomas - regrets

  • @Bonnie Gordon

  • @Cory Nimer

  • @Thimios Dimopulos

 Goals

  • Prioritize new and awaiting more information tickets.

Links

Kanban boards:

Link to ArchivesSpace sandbox: http://test.archivesspace.org/

 Discussion topics

Who

Topic

Notes

 

Who

Topic

Notes

 

@Matthew Neely

Welcome

Meeting to focus on how Dev Pri can support @Thimios Dimopulos on community resources for Jira tickets.

 

@Thimios Dimopulos

Short overview of work to improve guidance on Jira tickets for feature requests and bug reports.

 

 

 

 

 

All

Comments and feedback on guidance for submitting feature requests:

  1. How to Request a New Feature

  2. Behavior Scenarios

  3. How to Report a Bug

Drafts for Jira templates:

https://docs.google.com/document/d/13_wnMbzmPJC_oCpzMztfr8ge35fdZEqhrq1wTqfSp4I/edit?usp=sharing

https://docs.google.com/document/d/1tdNVGPqBs2WMB_AOr4Vmbnv3u7gtnmoUkhRbRYinv7E/edit?usp=sharing

Open Question:

Should we make sure that the description Field of a Jira ticket contains the actual agreed requirements? Who should be able to edit that field.

 

 

All

Open discussion on how Dev Pri can support this work.

Please submit ideas and discussion topics here: https://docs.google.com/document/d/18DZGTJVq6AeZ9z-qWA_bDnc7bXs0xO9xOMBQRtO1stY/edit?usp=sharing

 

 

All

Consider Dev Pri restructing this feature request into several tickets to provide a benchmark for users to follow: ANW-923: Suggested AlertsClosed-Will Not Do

 

 

@Matthew Neely @Thimios Dimopulos

Next steps