I configured that jira-users group members can create issues.
And I want to give edit permission to jira-users but only if the issue hasnot a work log in it
Is this possible in JIRA 4.4.x
Thanks
So you can only edit an issue if work hasn't started on it? Tricky. I think I'd end up editing system-issueoperations-plugin.xml and changing the condition elements to add a new condition. The new condition would be a custom condition that checked whether the issue has at least one work log.
You can change issue permissions so that only assignee can edit this issue. So when developer starts work on the issue he assigns himself to this issue and only he can edit it.
Documentation is here - http://confluence.atlassian.com/display/JIRA044/Managing+Project+Permissions
Related
I have issue with filltering in admin/catalog/products when i want reset saved filters I am redirect to main admin dashboard.
I tried remove cache and sessions but problem is still same.
Same issue here :(
I created a different superadmin user, and it works fine... Something wrong with the first user, but I can't find where...
Edit :
Just solved my problem as folows :
went into DB, table ps_admin_filter
found the filter that caused issue
deleted the record
everything is back to normal...
I would be interested in how and why this happen if anyone knows...
I got an error on my Odoo like on the picture, I've checked the user already has access to the user group. It's very thankful if you can help me.
I need more information but whenever you parform the action you are doing a security record rule is trggered, you can try the hard mode, go to security record rules and disable one rule and try and re enable after.
I add this setting (see on the picture) on the user's group I want to give access and it's solved. Apparently it's because the user does not have access to Object ir.filters which most of my modules use this.
I can see that getRecord call has CREATEORREAD action. Is it possible to make it read only? I need it to properly limit client permissions.
Thank you in advance!
Do you mean to avoid creating it if user does not have permissions? If the user does not have permissions for UPDATE or PATCH this will stop him from being able to update anything, but we don't yet have an individual READ action to avoid the record from being created initially. We'll raise that as an issue and try implement it soon.
Edit:
Issue created on github
We have a Problem with Absences:
A User who created an Absence can not edit the Absence after wards :(
After a user's Absence was approved he/she can still delete the absence :(
How to set the permissions for absences?
I understand your absence is controlled by a workflow, is that correct? There are two parameters controlling the behavior, so the correct solution would be to create copies of the permission functions and to set the parameters AbsenceNewPageWfEditButtonPerm and AbsenceNewPageWfDeleteButtonPerm accordingly. Please see the source code for details.
I found the file
packages/intranet-timesheet2/tcl/intranet-absences-procs.tcl
which contains the permission matrix im_absence_new_page_wf_perm_table
Unfortunately the permissions do not get effective immediately - a restart of project-open causes the permissions to be active.
A better solution would be desired - but at least it works :/
For a few days, the cloning of issues does not work anyway. I verified my permission scheme, and concerned users, can both create/modify issues, and modify reporters... but it still does not work.
The only change I made is the use of jira.permission.edit.user permission on each JIRA status in my workflow. In my permission scheme, I allowed users to modify users in general, but in my Workflow, using jira.permission.edit.users, I restricted this right for all status since the 2nd status... is that a problem ? do I have to allow cloning issue using any properties on each status ? anything else ?
I suceed to clone an issue... but the clone of my issue is my issue itself with original summary even I specified another one... Anyone has an idea ?
Any help greatly appreciated,
Thanks a lot,
Christophe
Those workflow properties are not particularly well documented. I'd use the permission scheme instead if you can