Support
To check known issues (or if you want to file one), view this app's issue tracker.
To learn more about the app, you should:
- Read the documentation.
- Investigate the wiki.
If you are a developer, you can help fix the problem yourself by:
- Downloading the source code.
This is a supported app, so you may contact the vendor (or support contact) for help:
Description
1
1
2
2
3
3
More details
This plugin simply installs a servlet that advises that the Behaviours plugin has merged with Script Runner for Jira.
Script Runner can be downloaded from the marketplace. Once done, this plugin should be uninstalled.
Version history
0.5.14Jira Server 6.3 - 6.3.152014-07-10Updated to point to the 3.0.0 version of Script Runner. No release notes.0.5.12Jira Server 6.2 - 6.2.72014-06-09New version availability information Important:
The behaviours plugin will be merged with Script Runner. The merged version will be released approximately when Jira 6.3 is released.
However you can get a preview version which works with Jira 6.2 from the attachments of https://jamieechlin.atlassian.net/wiki/display/GRV/Upgrading+to+3.0.
The behaviours plugin allows an administrator to create one more or behaviours, which can be thought of as "Behaviour Schemes". A behaviour defines how fields behave. Some examples of behaviours are:
- Making a field mandatory depending on other data entered in to the form
- Making a field read-only dependent on user role or group
- Doing server-side validation of field data, before the form is submitted
- Setting a field value dependent on other form data
Please see the comprehensive list of examples on the wiki page for more ideas.
0.5.10Jira Server 6.0 - 6.1.92013-09-29Compatibility with jira 6.1 Important:
The behaviours plugin will be merged with Script Runner. The merged version will be released approximately when Jira 6.3 is released.
However you can get a preview version which works with Jira 6.2 from the attachments of https://jamieechlin.atlassian.net/wiki/display/GRV/Upgrading+to+3.0.
0.5.9Jira Server 6.0 - 6.0.82013-09-20Client side fixes, mostly around only disabling inline edit just where required Inline edit is now disabled only where a field is added in a behaviour.
So if you have a behaviour of the sort where field B depends on field A, typically you would have a server-side script for field A. Now you should also add field B to the behaviour config, even though you won't give it any special "behaviours".
This will prevent both A and B being inline edited.
Disabling inline edit now also works in the issue navigator, and immediately after updating an issue (ie where a full page refresh doesn't happen).
0.5.6Jira Server 6.0 - 6.0.82013-08-20Prevent plugin being disabled Fixes critical issue whereby the plugin would disable itself after viewing the custom fields page.
0.5.5Jira Server 6.0 - 6.0.82013-07-08fixes a problem display behaviours with role restrictions No release notes.0.5.4Jira Server 6.0 - 6.0.82013-07-05Compatibility with jira 6.0 No release notes.0.5.3Jira Server 5.1 - 5.2.112012-11-12Compatibility with jira 5.2 No release notes.0.5.2Jira Server 5.1 - 5.1.82012-11-04Minor bug fixes The Behaviours plugin does not support inline editing. If a behaviour is mapped for a particular project/issue type, it will disable inline edits for that issue.
Alternatively, you can disable inline edit for your entire instance from the General Configuration administration screen.
0.5.1Jira Server 5.1 - 5.1.82012-11-01Jira 5.1 compatibility The Behaviours plugin does not support inline editing. If a behaviour is mapped for a particular project/issue type, it will disable inline edits for that issue.
Alternatively, you can disable inline edit for your entire instance from the General Configuration administration screen.
0.5.0Jira Server 5.0 - 5.0.72012-02-09rearchitected to make compatible with script runner 2.0 No release notes.0.5.0Jira Server 4.4 - 4.4.52012-02-09rearchitected to make compatible with script runner 2.0 No release notes.0.4.9Jira Server 5.0 - 5.0.72012-02-04compatibility with jira 5.0rc3 plus fixes for cascading selects No release notes.0.4.9Jira Server 4.4 - 4.4.52012-02-04fixes for cascading selects No release notes.0.4.7Jira Server 5.0 - 5.0.72011-10-23compatibility with jira 5.0beta1 No release notes.0.4.7Jira Server 4.3 - 4.4.52011-10-23minor fixes plus jira 5 compatibility No release notes.0.4.6Jira Server 4.3 - 4.4.52011-10-12Global behaviours You can now associate multiple behaviours with a project, and define *Global* behaviours.
0.3.4Jira Server 4.2 - 4.3.42011-03-23Bug fixes 0.3.3Jira Server 4.2 - 4.3.42011-03-20Compatibility with jira 4.3 This release is just for a couple of fixes that make the plugin compatible with jira 4.3
0.3.2Jira Server 4.2 - 4.2.42011-02-07Minor fixes. No release notes.0.3.1Jira Server 4.2 - 4.2.42011-01-27Compatibility for jira 4.2 No release notes.0.2.8Jira Server 3.13 - 4.1.22010-01-19radio button and checkbox javascript problems - Set radio button and checkbox values.
- Ability to remove the validity indicator entirely.
- Warning when no mappings are defined.
- A bug prevented applying a behaviour just to sub-task issue types, this is now fixed.
- Fixed a bug whereby the "requiredness" was not getting correctly removed from radio buttons in IE.