Forming issue template (from 1962)

[gigamorph]

Problem Description: Describe the problem to solve or enhancement being requested.

Expected Behavior/Solution: Describe the solution to the problem or the expected behavior.

Requirements: List of details required for the completion of the issue or requirements for the feature/bug. This can also include requirements that lie outside of the teams such as new design docs or clarification from an outside source.

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

• [ ] Wireframe/Mockup - Heather
• [ ] Committee discussions - Sarah
• [ ] Feasibility/Team discussion - Sarah
• [ ] Backend requirements - TBD
• [ ] Frontend requirements- TBD
• [ ] Questions
• List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

• Example endpoints from LUX to use for development and testing, if applicable.

Dependencies/Blocks:

• Blocked By: Issues that are blocking the completion of the current issue.
• Blocking: Issues being blocked by the completion of the current issue.

Related Github Issues:

• Issues that contain similar work but are not blocking or being blocked by the current issue.

Related links:

• These links can consist of resources, bugherds, etc.

Wireframe/Mockup: Place wireframe/mockup for the proposed solution at end of ticket.

[jffcamp]

The ticket template exists in each of the repos. I suggest we close this.