Just a note, based on past experience - make sure your JQL conditions return only limited and relevant results (try limiting by issue type as well, for example). This is because this JQL will be made to all tickets in your DB, so may influence overall performance.
Where you are typing the condition is for code... there is a JqlQueryCondition, but it is a condition, rather than a validator. Which means the user won't see the action at all. If you want a validator you will probably need a custom validator that runs that query.
Does not sound like the best idea though, although I don't know what your process requires.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes that's a Validator, my mistake. As Jira doesn't provide a WIP limit per a user, I have to implement this somehow. And Yes this is our Kanban implementation based on the teams capacity so WIP Limit per person is crucial for us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.