Discussion:
validator plug-in to check security levels.
f***@atlassian.com
2011-07-19 10:03:02 UTC
Permalink
Hi All,

As my requirement is i want develope a validator plug-in it work like

if the user is not there in the security level i won't allow the transition and throwing error msg.

if he is in security level than i want allow the transition.

for doing this what steps i have fallow.

i mean class and code to chek security level b/w current user.

Thanks and Regards,
Babu.
--
Post by sureshg - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=55299
f***@atlassian.com
2011-07-19 11:09:53 UTC
Permalink
Post by f***@atlassian.com
if the user is not there in the security level i won't allow the transition and throwing error msg.
If a user is not in the security level, *they can't even see the issue*, let alone use any transitions, so there's no need for this.

Unless I'm completely misunderstanding the requirement. If so, could you explain further?
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=55299
f***@atlassian.com
2011-07-19 11:18:50 UTC
Permalink
Hi Nic,

Yes ,if the user is not in the security level we can't give permmision like even creating issue.
and we have to throw the message like "Dont't permmisions".


Regards,
Babu.
--
Post by sureshg - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=55299
f***@atlassian.com
2011-07-19 11:25:42 UTC
Permalink
So there's nothing to do. Ok.
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=55299
f***@atlassian.com
2011-07-20 07:47:01 UTC
Permalink
Hi Nic,

requiremt is

plug-in It should to allow to create or not a specific according the security level that the user is configured.


Security Level is configured by groups. So,validator plugin that allows or not create issues in jira according the Security Level configuration.


example ::Customer is going to create defects in JIRA, they should be allowed. However, they should can create issues such as Task, Testing Task, Implementation Task...


Regards,
Babu.
--
Post by sureshg - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=55299
f***@atlassian.com
2011-07-20 08:46:18 UTC
Permalink
No, I'm still not understanding it. You're rambling about security levels which are there to hide issues from users. Your specification seems to be "stop users from doing stuff to issues" which is already done by security levels because the users who are in the wrong groups won't be able to see or work on issues in the first place.

Now you've started talking about something utterly different, you haven't mentioned it before, and you seem to be very confused about processes inside Jira and on a human level.
Post by f***@atlassian.com
example ::Customer is going to create defects in JIRA, they should be allowed. However, they should can create issues such as Task, Testing Task, Implementation Task...
Fine - use the "create" permission to stop them
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=55299
Loading...