Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use jira issue to get bug status #15359

Merged
merged 1 commit into from
Jun 7, 2024

Conversation

jameerpathan111
Copy link
Contributor

Problem Statement

We have migrated to Jira and some of the bz have been closed without being fixed/resolved. It's causing is_open function to return false status and we're now running the assertion which fails.

Solution

  • Use Jira issues to get the bug status

Related Issues

@jameerpathan111 jameerpathan111 added the No-CherryPick PR doesnt need CherryPick to previous branches label Jun 6, 2024
@jameerpathan111 jameerpathan111 self-assigned this Jun 6, 2024
@jameerpathan111 jameerpathan111 requested a review from a team as a code owner June 6, 2024 19:40
@JacobCallahan
Copy link
Member

@jameerpathan111 why the choice not to cherry-pick this?

@jameerpathan111 jameerpathan111 added CherryPick PR needs CherryPick to previous branches 6.13.z Introduced in or relating directly to Satellite 6.13 6.14.z Introduced in or relating directly to Satellite 6.14 6.15.z Introduced in or relating directly to Satellite 6.15 and removed No-CherryPick PR doesnt need CherryPick to previous branches labels Jun 6, 2024
@jameerpathan111
Copy link
Contributor Author

@jameerpathan111 why the choice not to cherry-pick this?

Marked for cherry-pick.

@shweta83
Copy link
Contributor

shweta83 commented Jun 7, 2024

Should we need to update docstring too for Bugzilla to Jira?

@devendra104
Copy link
Member

Should we need to update docstring too for Bugzilla to Jira?

I feel this should be updated but we can cover it separately @jameerpathan111 what do you say?

@jameerpathan111
Copy link
Contributor Author

Should we need to update docstring too for Bugzilla to Jira?

I'd suggest doing that in a separate PR. For now, let's merge it as it is.

@devendra104 devendra104 merged commit 7d1e850 into SatelliteQE:master Jun 7, 2024
8 checks passed
github-actions bot pushed a commit that referenced this pull request Jun 7, 2024
github-actions bot pushed a commit that referenced this pull request Jun 7, 2024
jameerpathan111 added a commit to jameerpathan111/robottelo that referenced this pull request Jun 7, 2024
devendra104 pushed a commit that referenced this pull request Jun 7, 2024
Use jira issue to get bug status (#15359)

(cherry picked from commit 7d1e850)

Co-authored-by: Jameer Pathan <[email protected]>
omkarkhatavkar pushed a commit that referenced this pull request Jun 7, 2024
omkarkhatavkar pushed a commit that referenced this pull request Jun 7, 2024
Use jira issue to get bug status (#15359)

(cherry picked from commit 7d1e850)

Co-authored-by: Jameer Pathan <[email protected]>
jyejare pushed a commit to jyejare/robottelo that referenced this pull request Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.13.z Introduced in or relating directly to Satellite 6.13 6.14.z Introduced in or relating directly to Satellite 6.14 6.15.z Introduced in or relating directly to Satellite 6.15 CherryPick PR needs CherryPick to previous branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants