11:30am-1pm ET
\uD83D\uDC65 Participants
Dillon Thomas - regrets
\uD83E\uDD45 Goals
Prioritize new and awaiting more information tickets.
Links
Kanban boards:
New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
\uD83D\uDDE3 Discussion topics
Who | Topic | Notes | |
|---|---|---|---|
Welcome | Meeting to focus on how Dev Pri can support Thimios Dimopulos on community resources for Jira tickets. | ||
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: Drafts for Jira templates: https://docs.google.com/document/d/1tdNVGPqBs2WMB_AOr4Vmbnv3u7gtnmoUkhRbRYinv7E/edit https://docs.google.com/document/d/13_wnMbzmPJC_oCpzMztfr8ge35fdZEqhrq1wTqfSp4I/edit 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 - Getting issue details... STATUS | ||
Next steps |