|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Reference
|
|
|
|
This issue is related to:
|
|
CMMT-7
Project based configuration of rules
|
|
|
|
|
|
|
|
This plugin would be instantly useful to me if it was not a sitewide switch to turn on and off. I need the ability to 1) activate by Project, and
2) specify different repositories.
Some repositories/projects would require this kind of restriction, others would not, but all use SVN and Jira.
|
|
Description
|
This plugin would be instantly useful to me if it was not a sitewide switch to turn on and off. I need the ability to 1) activate by Project, and
2) specify different repositories.
Some repositories/projects would require this kind of restriction, others would not, but all use SVN and Jira. |
Show » |
|
New Feature
Critical
Allow activation by project / repository
I would actual decribe this issue somewhat differently. If you want it switchable by repository that is simply to accomplished since each repository has it owns hooks directory. Simply only add the hook to the repositories for which you want the checks to be made.
The problem is more on the JIRA end since you can only configure which specific check are made on a global basis not on a project basis. In my case I wanted some projects to only do the issue key validity check, and other projects to do all three check (issue key validity, issue not resolved, and committer = issue assigne).