Let assume that I have several changes in review state in Gerrit.
Can I be notified (via email) when "merge conflict" appears on one of my changes?
Have a nice day,
Adam
You can't receive this information by e-mail (unless you wrote a script to automate this task using REST) but you have other good options:
Search field
You can use the Search feature to search for the following:
owner:username AND status:open AND NOT is:mergeable
This will show your open changes with conflicts.
My Menu
You can add a menu entry for the search showed above at Settings > Preferences > My Menu adding the following URL:
#/q/owner:username+AND+status:open+AND+NOT+is:mergeable
I want to prevent my users from logging work once an issue gets to a particular status. How can I accomplish this?
I have a post-function in my workflow that sets the Resolution, but the "Log Work" item in the More menu still shows up.
I don't see in the Project or System administration any options about it.
You can accomplish this by setting jira.issue.editable to false in the properties of the status in the workflow.
Find the active workflow that applies to the issues you wish change. This is most easily done by either: going to the 'Workflow Schemes' admin page, then clicking on the Workflow link in the row applying to the issues' project and issue type, or clicking View Workflow in the Issue View.
To edit the workflow, you will need to either create a copy of it (if using the default jira system workflow) or edit the draft of the workflow.
In the Workflow Editor, for the 'Closed' step, click View Properties (in Text mode) or Properties (in Diagram mode) to see the step properties.
Editing issues in the selected step is enabled by default, or you will see a jira.issue.editable property with value true. Either create the value or chang the property value to false.
Publish your draft workflow, or if editing a copy, activate the workflow by creating a new workflow scheme associated with the edited workflow, and then associating it with your project.
Reference: https://confluence.atlassian.com/jira/allow-editing-of-closed-issues-138704.html
I have certain issues that are secure and should not be viewed by all roles. I'm looking for a way to only show the summary on the view screen but no other details unless a certain role views it. Some sort of way to flag an issue on creation to hide certain fields.
There may be other easy ways to do this.but one solution that comes to my mind is use of Behaviours plugin.using this plugin can hide fields if certain user logged into the system.
you can follow steps like this..
1.install Behaviours plugin and create new behaviour then add mappings and go to the fiels and do the relevant configurations...
2.then you can add fields you want to hide and add conditions to them. then there is a option to add certain user roles in the condition configuration page.
3.then click on the hide link on the Field page.
Note-the Behaviours plugin is part of the Script Runner plugin now.you can use either Behaviours plugin s or Script Runner plugin
How can i stop anonymous user to view my project activities in gerrit. I have googled enough but could'nt find what are exact files which are called Access Control List for project.
If you want to disallow anonymous users to browse/read/search all the changes of a certain project, you just have to remove the Read permission for anonymous users from the project.
In order to be allowed to modify permissions, you have to be either Administrator or owner of that project.
To disallow anonymous browsing, follow these steps:
Go to Projects > List in the menu
Click on the project's name (or All-Projects, if you want to modify the default for all projects (requires being Administrator))
Choose Access in the submenu and hit the Edit button there.
From *Reference: refs/** remove in the Read section the ALLOW Anonymous Users using the X on the right side.
Hit Save changes
We have some trainees and we would like to give them some introductory tasks in JIRA.
We are using JIRA version 4.4.
What is the least intrusive way (avoiding creating global groups or permissions, if possible) in JIRA to achieve the following:
restrict the trainee user account so he can browse only a certain single project and no other projects are visible to him in menu, dashboards etc.
give this user the same permissions as default jira-developer has, but only for his associated project
?
Those trainees might leave after a month or two, so we would like to be able to delete their accounts later as easy as possible (without any linking issues, like "You cannot delete this because it is associated with that"...).
I tried to add one of the trainee accounts to a project using People tab. I added this user to Developers and Users sections, but still this user has a message:
"You do not have a permission to log in."
when trying to log-in.
If I add this user to jira-users group, he can log-in, but he is able to see all the projects.
The problem I found with JIRA permissions is that core administration elements are strewn all over the place. Its frustrating to find options which other guides allude to.
So, here is a guide detailing where to find each section required for security permission setup:
1) Create a new group (restricted to project xyz group).
Click User management in top right (click the cog icon) > login as Administrator > click Groups (left menu)
Add group, self explanatory > Name = restricted to xyz group (or whatever you like)
2) Create a new permission scheme (Restricted to Project XYZ permission scheme)
From Administration area > Click Issues > Permission Schemes
Copy the default scheme as the guide says, > Click "copy" next to "Default Permission Scheme".
Now this part takes some time. I deleted every single permission, then clicked "add" next to the below items.
add > Click "Group" Radio Button > select your group "restricted to project xyz group" etc
Hint: I middle mouse clicked each item open all at once, first to delete, then to add. Makes it less tedious.
Here are the items I Assigned to my group:
Project Permissions > Browse Project
Everything under "Issue permissions" section
Comments Permissions > Add Comments
Comments Permissions > Delete Own Comments
Comments Permissions > Edit Own Comments
if using time tracking:
--> Time Tracking permissions > Delete Own Worklogs
--> Time Tracking permissions > Edit Own Worklogs
--> Time Tracking permissions > Work On Issues
I'm not sure if these are "correct" but it works for me.
3) Link the permission scheme with project XYZ
Click Projects > Select your Project (project XYZ) > Click "Administration" at top of screen (Next to overview) > Click Permissions (left menu) > Click Actions > Select Use a Different Scheme
Why, do I have to go into the project to do this? It should be available via the Administration area under project. This took me 5+ minutes to find just now even though I've done it before.
4) Grant the Global Permission "JIRA users" to the group "restricted to project xyz group" so they will be able to log in.
Go back to Administration area > Click Cog top right > Click System > Click Global Permissions (left menu)
Add Permission > Select Permission = JIRA Users, select Group = restricted to project xyz group (etc)
After this you should see your group appear next to "JIRA Users" just click View users, then invite/add the users as appropriate with your group selected.
That's all for now, I hope it includes everything, its all I could remember. Hopefully it saves someone else from the suffering i went through ;)
It depends which groups have the Developer and User project roles. By default these are jira-developers and jira-users. I would create a new project TRAINING and grant the Developers and Users roles to the trainee user ids explicitly. Now they can play in that project.
The harder parts are to restrict them from the other projects yet still allow them to log in. If the default groups are in use then do not add them to jira-users or jira-developers. You will have to define a jira-trainees group and add to the Global Permissions to allow them to log in.
Come to think of it, if you've ended up defining a jira-trainees group then you might as well use it in the project roles instead of their individual user ids. Once this is all set up you only have to add a user to jira-traininees, make sure they're not in jira-developers and jir-users and you're ready to go.
I wrote a tutorial on how to do this as it's so difficult to do especially for casual users.
Unfortunately you have to create a group and permissions scheme (and learn how to unhook the users group from the default permissions scheme, but I've laid it out really easily here so you'll not find an easier guide:
http://testigniter.blogspot.co.uk/2013/03/setting-up-jira-for-single-project-user.html
mdoar's answer has the guts, but here's a more step by step answer, specifically for the "You do not have a permission to log in." part.
Let's say you are logged in to Administration and there is a group 'My group for project X' and some users are assigned to this group.
1. Go to Users -> Global Permissions
2. Have a quick read about "JIRA Users"
3. In the "Add Permission" section choose "JIRA Users" as "Permission" and your group as "Group" and hit add.
4. All users from 'My group for project X' should now be able to log in.
For other access problems you may find "Premission Helper" useful (just look for it in the Administration Quick Search in the top right corner).
I did the following:
Created separate group for users allowed to see the project (Site Administration -> User management -> Groups
In Jira Admninstration -> Global Permissions added this group to "Jira users"
In the project's administration -> Roles added this group to "Users" project role
Created an user in this group and removed it from "jira-users" group. Without adding global permissions this would remove this user from accessing Jira at all
Worked like a charm (I hope), no annoying permissions scheme creation was needed