Hi!
I've setup up an automation rule that applies a "template" each time a new Epic is created. The problem is that the Epic contains a table, I'm not sure how to apply this formatting. Here is an example of what I'm trying to add to the description:
Problem:
Pain point:
XXX
Strategy:
XXX
Objective:
XXX
Definition of ready:
[] Problem defined
[] North star metrics defined
[] Kick-off scheduled with required and optional stakeholders
Solution:
Open questions:
Question | Answer |
|---|
Are there any sales or contract dates that the team should know or are working towards? | |
How does this scale to other staff groups e.g. AHP, Nursing? | |
Are there any known dependencies? | |
Are there any new designs needed? Are there opportunities to remove any confusing UX flows? | |
Should we displaying audit trails in the UI? | |
Are there ways we can introduce better standards? | |
Are there any opportunities to pay down stale code or tech debt in this space? | |
Will decisions in this impact performance? Design as this scales and/or app load? | |
Designs (UI/UX, Technical, Flows):
XXX
Decisions made:
XXX
Release phases:
XXX
Definition of done:
[] Problem or pain point alignment (stakeholder alignment)
[] Solution designed
[] Internal communicate of what’s in scope and what the phase(s) are
[] Solution built
[] Release notes drafted for external communications (stakeholder email, Beamer, QX release notes)
[] Update existing FAQs in Help Centre or create new page(s) when applicable
[] Testing included
[] Observability created to be able to measure (usage and/or data alignment)
Measure:
XXX
