Comments (3)
Hi, I was thinking about the detection of the changes in issues in resolved state.
Is it mainly about the creation of *.drl rules and tests for them ?
I am not sure about what kind of changes should flare up the sirens.
Addition of the PR after issue is in resolved state is obvious, however the change of state is the one I am not sure about. What kind of change of state it should be ?
Because I think for example the change of state from "Resolved" to "Ready for QA" and from "Ready for QA" to "Verified" are allowed.
from bug-clerk.
Not sure about first part. Second, with transition is correct.
Imagine that you have upgrade JIRA, all fixes have been merged, you get tag from dev, tell prod to do magic and give you artifacts. All while someone link another fix to upgrade JIRA(this can happen later on). Unless this new JIRA is also pushed into Sprint it will dangle unless RC notices it.
from bug-clerk.
Implemented ! Will be part of 1.0.0 release.
from bug-clerk.
Related Issues (20)
- Check Request #38 - Issue attached to payload but not assigned to anybody HOT 1
- Upgrade drools from 6.5 to something better (ie. 7.4.1.Final) HOT 3
- Fix dependency convergence HOT 5
- Refactor mockBug into mockBzIssue for consistency and clarity purpose HOT 1
- Evaluate Helpers - introduce common, object to allow greater detail of error? HOT 3
- Get ride of the AphroditeClient
- Don't null check Optional variable HOT 1
- Drools 7 - does it support more nicely stream and Optional ?
- FixVersionAndSprintMustMatchBetweenSiblings#fixVersionAndSprintNotMatchingBetweenSiblings is wrong HOT 2
- Check Request #39 - Issue state is either MODIFIED or ASSIGNED after PR was closed HOT 1
- Check Request #40 - Issue in on the payload but is missing some acks HOT 1
- HighPriorityIssueNotAssigned should only be triggered for Critical and Blockers, not Major HOT 1
- Migrate unit tests to JUnit5 ?
- Wrong HighPriorityIssueNotAssigned output format. It needs a blank space between the message and level HOT 1
- The bug clerk is mistaken about unassignement HOT 1
- Implementing Checks to tool CVE handling process HOT 1
- Check Request #41 - not allow multiple PRs against different repos. HOT 3
- Message enhancements HOT 2
- Upstream checks should NOT be limited to BZ issue
- IllegalFormatClassException during build HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bug-clerk.