-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
10
-
We need the ability exclude commits by commit message using regular expressions. For example, we want any commit message that starts with "Merged from" to be excluded from being read in from the repository because we don't need to review merged code and don't want the all those lines messing up the code review statistics/reports. This would be in addition to the Include/Exclude Paths to control which parts of the repository will be indexed.
- is related to
-
- Closed
- is superseded by
-
- Future Consideration
- relates to
-
- Not Being Considered
[CRUC-6293] Add ability to exclude commits based on commit message
David Jackson
added a comment - In my case I would like my workflow to use an "Unreviewed Code Condition" to transition only if there are no unreviewed changesets. It works great, except that the presence of a merge commit means either I can't transition or have to review those changesets.
David Jackson
added a comment - In my case I would like my workflow to use an "Unreviewed Code Condition" to transition only if there are no unreviewed changesets. It works great, except that the presence of a merge commit means either I can't transition or have to review those changesets. 
prabhakaran rk
added a comment - Any update on this feature. if we have this feature implemented it will be very useful
prabhakaran rk
added a comment - Any update on this feature. if we have this feature implemented it will be very useful 
Sven Schott
added a comment - We have the same requirement to exclude commits from some of our auto-merged branches. It creates a lot of noise in Crucible and Fisheye.
Sven Schott
added a comment - We have the same requirement to exclude commits from some of our auto-merged branches. It creates a lot of noise in Crucible and Fisheye. This function would be a big help for me too.
I have ticket links in the tag-commit messages (for the version changelogs).
But I dont want that these commits appear in the jira sources tab of the ticket itself. And it is no solution to exclude the whole tags branch.
So I want to
- block all commits to the tags folder from appearing on the sources tab
- be able to present a link to the fisheye server to this tag as a backreference.
For some reasons I also need to exclude a massive commit from my Fisheye report.
May be by excluding a commit with more than specified lines of code?
Would love to see such a feature.
Kevin Shine
added a comment - Have the same requirement 
Martin Bagnall
added a comment - I would like this to be implemented too.
In my case, I want to exclude the commits to pom.xml files performed by the Maven Release Plugin every time a new release is generated.The problem is the same as Kevin's - these do not need to be reviewed but are skewing the statistics in Crucible.
Martin Bagnall
added a comment - I would like this to be implemented too.
In my case, I want to exclude the commits to pom.xml files performed by the Maven Release Plugin every time a new release is generated.The problem is the same as Kevin's - these do not need to be reviewed but are skewing the statistics in Crucible.
Kevin Schmidt
added a comment - Please assign this issue to a developer. It is a big deal for us. Thanks.
Kevin Schmidt
added a comment - Please assign this issue to a developer. It is a big deal for us. Thanks. This is a big deal because our project managers want to make sure that we have 100% code reviewed each week. Each time we create/delete a branch or merge code it messes up the code review percentage numbers. This is our #1 issue with Crucible. We are a Fortune 50 company. BenefitExpress is a $3 billion/year application. Please make this high priority.
Kevin Schmidt
added a comment - - edited This is a big deal because our project managers want to make sure that we have 100% code reviewed each week. Each time we create/delete a branch or merge code it messes up the code review percentage numbers. This is our #1 issue with Crucible. We are a Fortune 50 company. BenefitExpress is a $3 billion/year application. Please make this high priority. 
Hi everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not being considered.
Excluding revisions brings significant impact on data consistency (e.g. how to make a diff if a revision is missing). For this reason we consider this only as a last resort and not as a mean to improve statistics or reports. Please read the FE-626 in which we describe in details plausible scenarios and how such exclusion could work.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Regards
Marek Parfianowicz
Development Team Lead
Fisheye/Crucible Team