I'd like to give our users free reign to create tasks under user stories, but I don't want them to create user stories themselves. In the permission scheme, there's only one permission: create issue. I can think of at least one hack to solve the problem, but I thought I'd ask the group their suggestions.
Not nice but a possible solution: You can add a validator to the Create transition that rejects a try to create an issue if the validation is negative. The user is able to select the issue type but gets an error message after clicking on create.
Another possibility may be a Javascript to remove the issuetypes from the selection. But that's nothing I can help with... :-)
Henning
The validator route is what i was considering as well, Henning. This just seemed like a common bit of functionality that I had hoped would have a more elegant solution or that I was overlooking in the core product.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
check following issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We work around this by putting the types you want to limit creation of in different projects. You can link issues across projects. Not a perfect solution. People have wanted issue level permissions pretty much from day one but it still isn't there. I don't expect it soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agree with you having a poxy project could do the job, but is not as nice as an integrated way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is similar to this question:
We have the same problem here we have 8 different issue types and public should only be able to create tickets of 3 different types the other ones should be only internally created.
A validator is not nice as the user get the feeling his ticket was "rejected" adn make another choice.
Thanks
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here weh have 8 different issue types and public should only be able to create tickets of 3 different types the other ones should be only internally created.
Thanks
Mark
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.