Details
Assignee
UnassignedUnassignedReporter
Craig McNallyCraig McNallyDevelopment Team
EurekaRelease
Trillium (R2 2025)RCA Group
TBDSprint
NonePriority
P3TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Craig McNally
Craig McNallyDevelopment Team
Eureka
Release
Trillium (R2 2025)
RCA Group
TBD
Sprint
None
Priority
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 13, 2025 at 6:44 PM
Updated February 28, 2025 at 4:24 PM
Overview:
There are two pages in the Best Practices section of the Eureka Developer Guide which need to be fleshed out with information:
Scope:
Provide the following:
Context - Description, links to relevant JIRAs where we’ve run into problems, etc.
Advice - Do this, instead of that…
Rationale - why should teams follow this advice, what are the practical implications (for devs? sysops? end users? etc.)
Cleanup any stub-related language, references to this JIRA, etc. Once the documentation exists these are no longer necessary.