Skip to content

Regarding scheduling conflicts to avoid #240

Closed
@ianbjacobs

Description

@ianbjacobs

We continue to want to include "conflicts to avoid" in the issue because GitHub makes it easy to view and navigate the issues by title.

However, we do not want to add a "Scheduling conflicts to avoid" session to the form, we want to add it after issue creation.

We want to avoid confusing people creating issues, so the label of the section should let them know this is for meeting planners only.

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