Hi team,
I have 1 project with 2 boards. One of the boards is strictly for our internal team to use for "Internal Projects" and the other is opened to the public for clients to cut an issue to us. The only thing is that when people within the company cut an issue to our team on the mainboard, I don't want them to see the option to cut an "internal projects" issue. How do I filter this in the JQL so that only our internal team can cut "internal projects" issues?
Thanks team!
@Edmond Dang you can use Validators to do this.
But you need to set rules in workflow to validate if certain users have the role or group to create issue.
If you need more details i can record a tutorial in youtube to you.
I hope I helped you.
If this post was helpful, mark it as Accepted solutions, so you can help others who may have the same difficulties.
If your question has not been resolved, please post again with more details.
Be aware that if you go this way, you will be creating an ugly user experience and you'll probably need apps to provide the validators.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well remembered at this point, thanks @Nic Brough -Adaptavist-
This solution I mentioned @Edmond Dang , would be if they are issuetypes like "Manager" or "Team", well focused on roles/functions. In issuetype generics like "Task", "Subtask", "Epic" , it will be very bad without add-ons to correct notify the users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gergely Groupama sorry for my abstence.
You still need the youtube tutorial ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Carlos Faddul !
Sure, if it is available.
We solved the problem we had with Scriptrunner scripts, but I am interested if there are other solutionas available.
Thanks in advance!
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gergely Groupama you can use issue security level + automation to do this :)
Or use validator in the workflow to block this type of create for only some users.
You can put a message text in the screen to avoid open too :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, @Carlos Faddul !
My organization is not familiar with the security level concept and we don't have automation so the first one is out.
The validator option never actually occurred to me... facepalm... I'll look into that and maybe we can avoid a script.
I'm not sure what you mean by the message text.. Just tell them "don't open certain issuetypes, please"? :D Or what?
Thanks,
G
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gergely Groupama validators can make your life easier :D
The message text it's like this, with background blue :D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, @Carlos Faddul !
The validator does indeed solve the issue!
It isn't the most elegant solution because a simple user would not understand the lack of permission error message.
So, I am interested how I can make one of those cool blue message texts... :D Can you help with that too?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Gergely Groupama , this is a field named "Message Custom Field"
You need only to use some tags of html/css in context to make pretty for users :D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You do not. If someone can create an issue in a project, then they can create an issue of any type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.