-
Spike
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
2
-
False
-
-
False
-
-
-
Pipelines Sprint CrookShank 44, Pipelines Sprint CrookShank 45, Pipelines Sprint CrookShank 46
Story (Required)
At present we need to add all the stories to the release pipeline manually in konflux but konflux has a tool "collector" which helps to automatically fetch all the Jira issues based on the JQL provided.
Background (Required)
<Describes the context or background related to this story>
Out of scope
<Defines what is not included in this story>
Approach (Required)
This story is to do a spike on the collector and try on stage build
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met