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 #24 - Fix version and Sprint must match between siblings(Upgrade-component fixes) #41

Closed
baranowb opened this issue Jul 26, 2016 · 3 comments
Closed

Check Request #24 - Fix version and Sprint must match between siblings(Upgrade-component fixes) #41

baranowb opened this issue Jul 26, 2016 · 3 comments
Milestone
0.9.0

Comments

@baranowb
Copy link
Contributor

If upgrade JIRA is in sprint X, for version X.x, same must apply to linked issues with category "incorporates" from upgrade JIRA.
@rpelisse
Copy link
Contributor

rpelisse commented Oct 4, 2016

Can you link to some example issues ? (a "good one" and a "bad one").

Also I assume that this check can NOT be used if there is not sprint associated to the issue (like for JBEAP-5865)

@baranowb
Copy link
Contributor Author

baranowb commented Oct 6, 2016

Upgrade: sprint 7.0.1, fix version 7.0.1.CR2
Children: Sprint 7.0.1, fix version [7.0.1.C1, 7.0.1.CR2,....,7.0.1.GA)

@rpelisse rpelisse changed the title Fix version and Sprint must match between siblings(Upgrade-component fixes) Check Request #24 - Fix version and Sprint must match between siblings(Upgrade-component fixes) Oct 19, 2016
@rpelisse rpelisse added this to the 0.9.0 milestone Oct 27, 2016
@rpelisse
Copy link
Contributor

rpelisse commented Dec 1, 2016

Implemented and released with Bugclerk 0.9.0.Final.

@rpelisse rpelisse closed this as completed Dec 1, 2016
rpelisse pushed a commit that referenced this issue May 29, 2018
@baranowb @rpelisse
Check Request #41 - not allow multiple PRs against different repos.
5b70d4e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.9.0
Development

No branches or pull requests
2 participants
@rpelisse @baranowb