♻️ Edited IssueTypeScreenSchemeMappingPayloadScheme

[ctreminiom]

1. Added the Description tag on the struct IssueTypeScreenSchemeMappingPayloadScheme
2. Closes IssueTypeScreenSchemeService: add description field when creating issue type screen schemes #131

[codecov]

Codecov Report

Merging #132 (9dc118e) into main (0e44336) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #132   +/-   ##
=======================================
  Coverage   99.94%   99.94%           
=======================================
  Files         158      158           
  Lines       11661    11661           
=======================================
  Hits        11655    11655           
  Misses          3        3           
  Partials        3        3           

Help us with your feedback. Take ten seconds to tell us how you rate us.

[iacabezasbaculima]

@ctreminiom It seems that you added the description field in a different struct.

I was referring to the following struct:

type IssueTypeScreenSchemePayloadScheme struct {
	Name              string                                       `json:"name,omitempty"`
---> add 'description' field here <---
	IssueTypeMappings []*IssueTypeScreenSchemeMappingPayloadScheme `json:"issueTypeMappings,omitempty"`
}

The struct above is used to create an issue type screen scheme by calling this API endpoint which supports passing a description.

Also, I think you may need to roll back this PR because the IssueTypeScreenSchemeMappingPayloadScheme used to specify issueTypeMappings does not support a description field passed in the Jira API endpoint payload schema.