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.

Sign up for GitHub

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

Jump to bottom

Check Request #21 - Loose matching of target release vs BZ payload name #36

Closed
rpelisse opened this issue Apr 27, 2016 · 1 comment
Closed

Check Request #21 - Loose matching of target release vs BZ payload name #36

rpelisse opened this issue Apr 27, 2016 · 1 comment
Labels
wontfix

Comments

@rpelisse
Copy link
Contributor

rpelisse commented Apr 27, 2016 •
edited
Loading

If an issue is a payload tracker, such as BZ1386335, the check will verify that the version mentioned in the subject (EAP 6.4.13) matches the one set for the issue (6.4).
@rpelisse
Copy link
Contributor Author

rpelisse commented Oct 26, 2016 •
edited
Loading

This is check will only be valid against BZ as there appears to have no payload tracker (as an issue) with JIRA. Thus I don't think it is worth it to implement it.

rpelisse pushed a commit that referenced this issue Dec 20, 2017
@baranowb @rpelisse
Check Request #36 - Identify JBEAP issue with a PR not matching Targe…
0f42cc3 
…t Release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rpelisse