OSD-30374: update long description based on SOP

[devppratik]

Updates long description based on SOP
The help command would now look like

╰─❯ go run . -S jira create-handover-announcement -h

Create a new Handover announcement for SREPHOA Project. To fill the fields, use the following instructions:

1. Cluster ID
	- If a specific cluster is affected, enter the ID (internal or external).
	- If not applicable: enter None, N/A, or All for fleet-wide impact.

2. Customer Name
	- Use the exact name from the output of the command you ran. Do not modify or abbreviate. Copy-paste exactly.
	- If not applicable: enter None or N/A
	Note : To find the Customer Name you can get it from ocm decribe cluster | grep -i organization or run the following command ocm get $(ocm get $(ocm get cluster $CLUSTER_ID  | jq -r .subscription.href) | jq -r '.creator.href') |  jq -r '.organization.name'

3. Version
Use the Openshift version number in the format:
	- 4.16 if it affects entire Y-stream versions
	- 4.16.5 if it affects a specific version

4. Product Type
Select the appropriate product type:
	- Choose Multiple if it affects the fleet
	- Otherwise, select the specific product involved

5. Description - Add a brief description of the announcement.

Usage:
  osdctl jira create-handover-announcement [flags]

Flags:
      --cluster string       Cluster ID
      --customer string      Customer name
      --description string   Enter Description for the Announcment
  -h, --help                 help for create-handover-announcement
      --products string      Comma-separated list of products (e.g. 'Product A,Product B')
      --summary string       Enter Summary/Title for the Announcment
      --version string       Affected Openshift Version (e.g 4.16 or 4.15.32)

[openshift-ci-robot]

@devppratik: This pull request references OSD-30374 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Updates long description based on SOP
The help command would now look like

╰─❯ go run . -S jira create-handover-announcement -h

Create a new Handover announcement for SREPHOA Project. To fill the fields, use the following instructions:

1. Cluster ID
  - If a specific cluster is affected, enter the ID (internal or external).
  - If not applicable: enter None, N/A, or All for fleet-wide impact.

2. Customer Name
  - Use the exact name from the output of the command you ran. Do not modify or abbreviate. Copy-paste exactly.
  - If not applicable: enter None or N/A
  Note : To find the Customer Name you can get it from ocm decribe cluster | grep -i organization or run the following command ocm get $(ocm get $(ocm get cluster $CLUSTER_ID  | jq -r .subscription.href) | jq -r '.creator.href') |  jq -r '.organization.name'

3. Version
Use the Openshift version number in the format:
  - 4.16 if it affects entire Y-stream versions
  - 4.16.5 if it affects a specific version

4. Product Type
Select the appropriate product type:
  - Choose Multiple if it affects the fleet
  - Otherwise, select the specific product involved

5. Description - Add a brief description of the announcement.

Usage:
 osdctl jira create-handover-announcement [flags]

Flags:
     --cluster string       Cluster ID
     --customer string      Customer name
     --description string   Enter Description for the Announcment
 -h, --help                 help for create-handover-announcement
     --products string      Comma-separated list of products (e.g. 'Product A,Product B')
     --summary string       Enter Summary/Title for the Announcment
     --version string       Affected Openshift Version (e.g 4.16 or 4.15.32)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[chamalabey]

/lgtm

[chamalabey]

@devppratik could you please run make verify-docs and push the changes again.

[devppratik]

@chamalabey The docs are now updated. PTAL

[joshbranham]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chamalabey, devppratik, joshbranham

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [devppratik,joshbranham]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@devppratik: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.