🚧Add ability to set the issue type

[CalvinWilkinson]

Complete The Item Below

• I have updated the title without removing the 🚧 emoji.

Description

Add functionality to the issue client to get and set the issue type value.

Note

Issue types are a new GitHub feature currently in public preview.

The client should be able to do the following:

1. Add functions to the Org client to create, retrieve, and manage issue types.
   • This is required before adding or changing the issue client. The issue client will use the org client functions.
2. Get the issue type from an issue using an issue number
3. Set the issue type from an issue using the issue number
   • First, this should check to see if the issue type exists.

Acceptance Criteria

The items to complete to satisfy the Definition of Done.

• All the unit tests have been executed and passed locally after the PR work is complete. (Why? Refer to 'Additional Information' below.)
• Function added to the org client to get data of all the issue types
• Function added to the org client to update a single issue type
• Function added to the org client to return a value indicating if an issue type exists
• Function added to the issue client to get an issue's issue type
• Function added to the issue client to set an issue's issue type
  • A check is done before setting the issue type of an issue before setting the issue type

ToDo Items

The items to complete to satisfy the Definition of Done.

• Add a change type label to the issue. Refer to the Change Type Labels section below.
• Add a priority label to the issue. Refer to the Priority Type Labels section below.
• Link the issue to the correct milestone (if applicable).

Issue Dependencies

No response

Related Work

No response

Additional Information:

Unit Tests

Reasons for local unit test execution:

• Unit tests might pass locally but not in the CI environment during the status check process or vice-versa.
• Tests might pass on the developer's machine but not necessarily on the code reviewer's machine.
• If you notice that the test status check has passed but the test failed locally, please notify a project maintainer!

💡Warning💡
If the unit tests pass remotely and are not executed locally, this means we could be letting a bug slip into production.
Though bugs will always exist in some capacity, we should all do our part to help prevent them from happening.

Change Type Labels

Change Type	Label
Bug Fixes	🐛bug
Breaking Changes	🧨breaking-changes
New Feature	✨new-feature
CICD Changes	♻️cicd
Config Changes	⚙️config
Performance Improvements	🏎️performance
Code Doc Changes	🗒️documentation/code
Product Doc Changes	📝documentation/product

Priority Type Labels

Priority Type	Label
Low Priority	low priority
Medium Priority	medium priority
High Priority	high priority

Code of Conduct

• I agree to follow this project's Code of Conduct.

[CalvinWilkinson]

Issue put on hold until the REST api has been updating to deal with issue types.