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
Related
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
In my implementation of JIRA, I have a custom field called Developer which gets populated automatically (username) whenever someone move the JIRA from Open to Fixed state. Now I want something similar for the Fixed to Reopen transition. That is, whenever the tester changes the status to Reopen, it should go back to the Developer or the Project Lead (in case the field isnt populated as the custom field can be overridden).
I tried to implement a post function, but there isn't a way where I can use OR criteria. Or is there a way?
You can do a Post Function on the transition using the Script Runner plugin if its a self-hosted JIRA instance which will allow you great flexibility in the logic to fill the target field in.
I finally managed to find a workaround for this.
Download the Workflow Enhancer for JIRA plugin (FREE). You would also need JIRA Suite Utilities (I had it installed already for some other customization)
In the Fixed to Reopen transition, add a Post Function and use Copy Value From Other Field to update Assignee from Developer field
Then add another Post Function underneath this where you need to use Universal Post Function. Here make the boolean condition as {Assignee}=="" and select Choose post function to execute: as Assign to Lead Developer
Publish the draft.
I've been trying to follow http://devs.valence.desire2learn.com/2013/02/15/remote-plugins-the-bookwidget-sample-2 to make sure we can get the demo running before continuing with development, however we've run into the problem where the sample instructions given don't mention a "System Test Link", and d2l won't allow us to create the widget without one.
What is this, and how can this be solved?
Edit: The system the client is using is 10.1
Looks like the "community" decided that my additions to Sarah-Beth's answer were not appropriate. So here's my edited answer in it's entirety:
The System Test Link is not a required value in order to create a new Remote Plugin. This behavior has been verified against both Desire2Learn 10.1 and 10.2 environments.
A System Test Link value is required in order to run automated tests using the Test button on the Create a New Remote Plugin form. If you click the Test button without populating that field, you will be alerted that a value must be entered in the System Test Field in order to proceed. But this alert does not prevent you from creating your Remote Plugin by clicking Save.
The only required values for a new Remote Plugin are a launch point, a name, and a build type (course builder, widget).
Note. The UI for this management tool can be a bit confusing. When you enter your information and click Save, the tool's UX prompts the browser window to reset to the top of the displayed page: if your browser window is not long enough to contain the entire form, you will not see the little message above the Save button that tells you your configuration has changed, and there's no apparent change in the form's state. Accordingly, you may think that you haven't saved anything when, in fact you have.
Provide the config for your plugin, ensure you have a launch point, a name, and a build configuration selected (at least), and click Save. Once the browser resets the viewport to the top of the form's page, you should be able to click Cancel to back out of the form and see your new plugin in the list of plugins.
We are aware of the discomfort in this form and are taking steps to improve it's UX.
The System Test Link is not a required value in order to create a new Remote Plugin. This behavior has been verified against a Desire2Learn 10.2 environment.
A System Test Link value is required in order to run automated tests using the Test button on the Create a New Remote Plugin form. If you click the Test button without populating that field, you will be alerted that a value must be entered in the System Test Field in order to proceed. But this alert does not prevent you from creating your Remote Plugin by clicking Save.
I would like to implement simple workflow system inside the Bestpractical RT.
My approach is:
Participant (RT user) creates or is given Workitem (Ticket) inside the Business Process (Queue)
OnResolve scrip checks change Ticket status to Open and change TicketOwner to next Participant.
OnReject scrip changes Ticket status to Open and gives it back to previous Participant.
My questions are:
- Is there good scrip examples to manipulate statuses?
- How can I debug scrips?
- How to disable built-in scrips for queues?
I read that it is possible to create a module for RT with actions which can then be called from scrips, but cannot find good documentation/examples. Please advise if you have one.
And the last question, how to enable developer mode in RT?
Thank you very much in advance,
Alexei
I'll assume you're running an RT version 4.0.x.
For the workflow you described, you probably want to create new tickets for each phase rather than having tickets set to resolved, then re-opening them. You can create new tickets in scrips to do this. You can also create link relationships between them like Depends On or Parent Child.
You can find user-contributed samples of various conditions on the RT wiki. You'll see a bunch of debug output for scrips if you turn on debug mode in your logging config. You can also put warn statements in code to see additional output in the RT logs. To disable scrips, edit the scrip and set the Stage to disabled. These built-in scrips are global, so if you want to set them per-queue, you can create scrips under the queue configuration to make them queue-specific.
The best examples of actions and conditions are the RT code itself. You can find documentation at the bottom of the main documentation page. From there, you can look in the lib directory in the RT code to see how the actions and conditions are implemented. It's generally easier to get started creating actions and conditions by selecting User defined and using the text boxes on the scrip edit page.
You can set devel mode in the configuration file. Make use you set these in RT_SiteConfig.pm, not Config.pm. You'll also want to set you log levels to debug.
The goal we'd like to achieve is allowing a customer to view a read-only dashboard which would display the status of only that customer's issue(s). This could be a default dashboard assigned to/associated with a particular group. Is there a way to configure a dashboard to accomplish that?
Thanks in advance for whatever help you can provide!
The edit permission is controlled by the permission scheme used by a project that issues are in. So to make the displayed issues read-only you'll need to decide which JIRA projects the issues come from and change the permission scheme for all those projects.
To create a read-only dashboard, you must edit the workflow (Project/Administration/Workflows/Scheme:Edit) in the (Flash-based) Workflow Editor.
I suggest that you start by cloning the default workflow and making changes to the clone (rather than editing the default).
There will be items in a "Global Transitions" list. By default, all members of the "users" group will have the power to execute these transitions (even if you have altered your project's Permissions Scheme to prevent read-only users from creating issues or comments, for example).
1> Remove all of the items in the "Global Transitions" list
There will be items in a "Statuses" list. The "Resolved" status is an implicit part of the "Done" global transition, so it needs to be added to the workflow.
2> Drag the "Resolved" item from the "Statuses" list to the workflow.
Creating a transition involves selecting one of the 3 buttons, grouped with the mouse-pointer button, on the upper left corner of the Workflow Editor.
3> Select a transition type (Straight Line, Polygonal Line, Bezier Line) using the above buttons.
4> Click (and release) on the starting point of the transition (for example, "In Progress"). An arrow will appear under the mouse pointer.
5> Click (and release) on the destination point of the transition (for example, "Done"). You will be prompted to give the transition a name (the text that you enter for this name will appear on a button, in classic issue views, that performs the transition), such as: "ChangeToDone".
The new transition is now available to everyone, unless you lock it down with some conditions:
6> Click on the gear-like button (to the right of the transition name) and select "View Conditions".
7> Click on "Add a new condition to restrict when this transition can be performed".
8> Select a condition (such as "Only Assignee Condition"), scroll to the bottom of the list, and click the "Add" button.
Now you should have a workflow transition that can only be performed by users who meet the required conditions.
Repeat the above steps to craft conditional transitions between all of the statuses that you use in your project.
To use your new workflow scheme with your project, click the "Switch Scheme" button (Project/Administration/Workflows/Scheme) and then click the "Associate" button.
Once the association process is finished, sign-in as a user that does not satisfy any of the transition conditions. You should be unable to perform transitions when signed-in as this user.