Set maximum issue count per month

[Purevdorj Nyamdorj]

Hi, All

Is it possible to define maximum issue that can be created per month by Project ?

For example : for IT project 2000 issues can be created per month, maybe finance project 200 etc,

Maybe using free plugins or something.

Regards,

Purevdorj

[Nic Brough -Adaptavist-]

The problem with doing that is that your users may have genuine issues that you are now stopping them from raising, so they get lost.  You shouldn't be stopping them raising stuff, just telling them that there is a limit to how much you can deal with!

Logging issue limits is not a good approach.  The right approach is to limit the amount of work done by the time you spend on it.  If, for example, your customer has a contract for "50 hours a month", then look to block your support people from moving issues into a "we are working on this" status when they've gone over the monthly limit.

Of course, that can be done if you work in a Kanban style - Kanban boards can limit the work in progress by card count.

[Purevdorj Nyamdorj]

Hi, there 

Our final purpose is to block people from creating issues when there are specific number of jira issues which are not finished and created by same user_group members.

Regards,

Purevdorj

[Purevdorj Nyamdorj]

is it possible to achieve this by using jira automation tool ?

When creating issue, it will count  jira issues which are not finished and created by same user_group members, and update local field. Then another tool will check that field and update issue status.

[Nic Brough -Adaptavist-]

No, Automation won't do that.

[Fabio Racobaldo _Catworkx_]

Hi @Purevdorj Nyamdorj ,

it is a strange request btw, my suggestion is to add your own validator on creation (in the related workflow) so that there is a check that avoid creation if the limit has been reached.

You need to develop that validator in a plugin or using something like ScriptRunner.

Fabio

[Purevdorj Nyamdorj]

Hi @Fabio Racobaldo _Catworkx_ ,

Thank for your reply. I see ScriptRunner is a paid plugin. Is there any other ways to achieve without any cost ?

Purevdorj

[Nic Brough -Adaptavist-]

No, you will need a scripting or custom app to do this.

[Purevdorj Nyamdorj]

Thank you all 

[Ollie Guan]

Hello @Purevdorj Nyamdorj ,

What is the purpose of doing this? It may be more helpful to clarify the rules to the user, rather than simply restricting them within the system.

[Purevdorj Nyamdorj]

Good day @Ollie Guan ,

For example in corporate, some departments can work in 1000 issues per month so they would not like to receive more requests than they can handle. So we want to put a limit within the system

[Nic Brough -Adaptavist-]

Stopping creation is the worst possible way to address this problem.  

Your requestors have legitimate requests, and stopping them creating them just because your team can't handle them.  

You should be managing this with queues, prioritisation, SLAs, reporting, and telling your departments that the number incoming does not matter.  Assuming a simple structure of developers who deal with the requests and their team leaders, then look at how they are working.  Developers generally don't care about the volume, their day-to-day is to simply deal with the next one.  Their team leads should prioritise (including maybe flagging things as "not this month"), and reporting upwards that their team is not able to deal with the volume, so they need more people, better processes, and trying to get the other areas to reduce the volume (self serve processes, knowledge bases, or just looking at where everything is so broken)