[Task 1 - Customer Scenario Checks] Replacing Migrated BZs docstrings token to Jira based

[jyejare]

Problem Statement 1

The customer scenario check is based on the Bugzilla today, but since bug management is moved to Jira and the bugs have been closed as CLOSED MIGRATED, the customer scenario check is broken.

Also, the new bugs are being created on the Jira, hence it's vital to update the test docstrings to have the details from Jira instead.

Solution 1

• Migrate all the bugs closed as CLOSED MIGRATED to get their latest updates from Jira as a new destination.

Also,
The BZs which are not migrated are kept for reference
Some of the tests have already covered the verified token and hence only the BZ reference is removed.

Next

• Step 2 / Next PR would switch the logic of customer scenario checks from BZ to Jira.

Notes

Why are we linking to the parent Jira to the automated test even though there are clones an subtasks?

• The today's focus is Just to remediate the broken customer scenario check based on BZ
• The fix_version was missing on some of the clones at the time of writing this PR
• Parents has the customer cases attached, whereas some clones don’t hence finding the link to customer scenarios is hard

The issue that could happen to link the test to parent Jira ?

• The broken status-based test collection or any other logic

Should we be needing the revisit, if some logic/implementation needs stricter status of a jira ids linked to the tests?

• Yes, we may. But for now, fixing the customer scenario checks is more important.

[vsedmik]

Just a nitpick - till now we are using uppercase :Verifies: everywhere, shall we stick to it?
(yes, I am aware of this)

[shweta83]

Ack

[jameerpathan111]

@jyejare Ack, but let's be consistent and use uppercase Verifies.

[shweta83]

@jyejare Ack, but let's be consistent and use uppercase Verifies.

I am in favor to not stick with case, and we have added ignorecase for the same reason so we don't have to worry about it.

[jyejare]

@jameerpathan111 @vsedmik @shweta83 Yes, Tokens are case-insensitive. I mean I would do it in this PR but cant promise this would be followed by everyone later. Since there is no impact of case here, let it be any case.