Date: Fri, 29 Mar 2024 06:26:18 -0500 (CDT) Message-ID: <1065076841.368.1711711578940@os-confluence.ncsa.illinois.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_367_1458466065.1711711578939" ------=_Part_367_1458466065.1711711578939 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
I have previously written a lightning talk introducing some helpful= patterns for writing JIRA tickets. It introduces some terminology, as = well as what should be expected from a fully-detailed ticket.
The purpose of this document is to supplement those definitions with exa= mples of breaking down larger work items to increase transparency into the = process and maintain forward momentum.
NOTE: If you do manage to tease out one or more new issues, link it back= to the original by clicking Link Issues and choosing "split from" or "spli= t to"
The following may not always be a bad thing, b= ut they can indicate an issue that can be further broken down
See https://digitial-= product-engineering.atlassian.net/browse/SIMPL-115
Descrip= tion Catalog of extractors that provide extractor name, description, version, au= thors, rating, comments. Acceptance Criteria - SIMPL None
Descrip= tion Catalog of extractors that provide extractor name, description, version, au= thors, rating, comments. Acceptance Criteria - SIMPL None
See https://digitial-p= roduct-engineering.atlassian.net/browse/SIMPL-41
Descrip= tion Dashboard of job operations where a space admin can view number of jobs run= ning, waiting, and failed. A user can also view the history of a job and se= e its log files, status events, messages, resource allocation (memory usage= , cpu usage). Acceptance Criteria - SIMPL None
Descrip= tion As a Developer, I want to be able to gain greater compute insights of my ex= tractors in real time to better optimize resource allocation and scheduling= so that I can better profile the behavior of my extractor Syngenta Comments: NCSA Comments: 1) UI/UX and backend dev: 2 weeks 2) API dev: 1 week Min Estimate (Weeks): 3 Max Estimate (Weeks): 3 Acceptance Criteria - SIMPL None
NOTE: this is not a full Story. We only know the who/what/why but nothin= g about the "how" or "where". This can cause the estimate of "when" (e.g. t= he story estimate) to be significantly skewed.