Added an example of how to add a label to an issue

[lucribas]

closes #441

Description

Add an example of how to add a label to an issue.

Information that is useful here:

• The What: What is your change doing?
• The Why: Why is your change useful/needed? What is your use case? (this helps us to understand the real world better)
• Type of change: Things like Bugfix, New feature, Code quality improvements, Dependency upgrade, Documentation, ...
• Breaking change: Yes or no? Backward compatible?
• Related to an issue: Does this fix or close an issue? Or is related in any kind?
• Jira Version + Type: Which Jira version and type (on-premise / cloud) you have used?

Example:

Let us know how users can use or test this functionality.

// Example code

Checklist

• Unit or Integration tests added
  • Good Path
  • Error Path
• Commits follow conventions described here:
  • Conventional Commits 1.0.0
  • The seven rules of a great Git commit message
• Commits are squashed such that
  • There is 1 commit per isolated change
• I've not made extraneous commits/changes that are unrelated to my change.

[andygrunwald]

Thank you.