Skip to content

[Ticket name] #5

@MNC27

Description

@MNC27

Please describe the context of the issue and/or what you want from the issue/ticket.
A clear and concise description of what the issue/ticket is for, possibly including content from the wider project of which it is a part.

Describe the solution you'd like
A clear and concise description of what you want to happen/the output you want.

Key requirements for the ticket
Assuming they're not big enough to warrant their own issue/ticket, provide clear and concise descriptions of any specific tasks required as part of the ticket. Use bullet points for clarity.

Dependencies
Provide a description of any dependencies for the ticket, including links to the relevant issue/ticket where appropriate and/or to the data required, and (if known) estimated dates for completion.

Deadline
If there is a specific deadline, note the date. If it is less precise than that, give a time frame (e.g. approximately two weeks).

Additional context
Add any other context or screenshots about the issue/ticket here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions