2nd test issue to test the setting of different fields

### Description of defect

This issue is to test that the new parsing code in the git2jira script correctly parses the issue header.
Each field is individually checked to ensure either valid data or n/a (or None) is added.

#### Target(s) affected by this defect ?

K64F

#### Toolchain(s) (name and version) displaying this defect ?
None

#### What version of Mbed-os are you using (tag or sha) ?

n/a

#### What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

Mbed-cli v10

#### How is this defect reproduced ?

This issue can be reproduced by creating a new issue in any repository using the new issue template and varying how much information is provided.

Start by locating the git2jira script and its issue-header parsing logic in the automation-testing repository. Create a test issue using the new issue template with varying field values, then verify that each field is parsed as valid data or n/a/None as described.

Written by the indexing model from the issue text.