Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change tickets missing ITIL fields #315

Open
6 tasks
jasonpagetas opened this issue Sep 23, 2024 · 1 comment
Open
6 tasks

Change tickets missing ITIL fields #315

jasonpagetas opened this issue Sep 23, 2024 · 1 comment
Labels
type::feature type for Issues and Merge Requests. Can also be used in discussion in comments and commits v1.2-beta Version Affected.

Comments

@jasonpagetas
Copy link
Collaborator

jasonpagetas commented Sep 23, 2024

There is no field in changes for impactcontent, this also needs to be applied via the API


EoF OP

Change tickets require the basic ITIL Fields. Add them. These fields are markdown fields.

Requirements

  • Analysis:

    • Field Impact
    • Field Control List
  • Plans:

    • Field Deployment
    • Field Backup
    • Field Checklist

Links

@jasonpagetas jasonpagetas added the v1.2-beta Version Affected. label Sep 23, 2024
@jon-nfc jon-nfc changed the title Change tickets require field for impactcontent Change tickets missing ITIL fields Sep 23, 2024
@jon-nfc jon-nfc added this to the v1.2 milestone Sep 23, 2024
@jon-nfc jon-nfc added the type::feature type for Issues and Merge Requests. Can also be used in discussion in comments and commits label Sep 23, 2024
@jon-nfc
Copy link
Member

jon-nfc commented Sep 27, 2024

removing from 1.2 until it's decided how these will be implemented.

@jon-nfc jon-nfc removed this from the v1.2 milestone Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature type for Issues and Merge Requests. Can also be used in discussion in comments and commits v1.2-beta Version Affected.
Projects
Status: Ready to Commence
Development

No branches or pull requests

2 participants