In some cases, this is necessary to call some methods or conveniently write conditions.
Examples:
In some cases, this is necessary to call some methods or conveniently write conditions.
Examples:
In some cases, this is necessary to call some methods or conveniently write conditions.
Examples:
In some cases, this is necessary to call some methods or conveniently write conditions.
Examples:
Fixed a display issue on the issue creation screen
Fixed a display issue on the issue creation screen
Fixed a display issue on the issue creation screen
Fixed a display issue on the issue creation screen
Fixed bugs with defining context and issue screen for displaying a message.
Fixed bugs with defining context and issue screen for displaying a message.
Fixed bugs with defining context and issue screen for displaying a message.
Fixed bugs with defining context and issue screen for displaying a message.
How to display the date in the correct format with $issueFieldRender?
How to show the multiline value of a text field with $issueFieldRender?
How to display the date in the correct format with $issueFieldRender?
How to show the multiline value of a text field with $issueFieldRender?
How to display the date in the correct format with $issueFieldRender?
How to show the multiline value of a text field with $issueFieldRender?
How to display the date in the correct format with $issueFieldRender?
How to show the multiline value of a text field with $issueFieldRender?
Examples for new functions: https://jibrok.com/docs/message-field/dynamic-templates-examples/
Examples for new functions: https://jibrok.com/docs/message-field/dynamic-templates-examples/
Examples for new functions: https://jibrok.com/docs/message-field/dynamic-templates-examples/
Special version for built-in support for Assets(Insight) API. Includes changes to the base version and additional functionality for working with Assets API.Please install only if you have installed Assets.
Examples for new functions: https://jibrok.com/docs/message-field/dynamic-templates-examples/
Removing the limit on the length of the JQL query in the conditions for displaying the message.
Removing the limit on the length of the JQL query in the conditions for displaying the message.
Bug fixes
Bug fixes
The darkening background did not disappear after closing the message.
The darkening background did not disappear after closing the message.
JQL conditions didn't work only on the view screen. Issue fixed now JQL conditions should work on all screens except creation screen.
JQL conditions didn't work only on the view screen. Issue fixed now conditions should work on all screens except creation screen.
Fixed the operation of the ComponentAccessor class in the message body. In the new version, the use of ComponentAccessor and all its methods should work correctly.
Fixed the operation of the ComponentAccessor class in the message body. In the new version, the use of ComponentAccessor and all its methods should work correctly.
Improved collaboration with the app: IssueLayout - Change the issue design
Improved collaboration with the app: IssueLayout - Change the issue design
Variables with information about the user's locale allow you to create messages in different languages. And each user will see the text in the language specified in his settings.
Variables with information about the user's locale allow you to create messages in different languages. And each user will see the text in the language specified in his settings.
Now you can display messages after the transition. Without adding a screen to the transition.
Code example: https://jibrok.com/docs/message-field/dynamic-templates-examples/ -> Check how long ago the transition was made. Show message after transition. (How to use $secAfterLastTransition)
New variables have also been added:
Now you can display messages after the transition. Without adding a screen to the transition.
Code example: https://jibrok.com/docs/message-field/dynamic-templates-examples/ -> Check how long ago the transition was made. Show message after transition. (How to use $secAfterLastTransition)
New variables have also been added:
Fixed bugs with displaying messages with custom styles and icons.
New display settings.
Fixed bugs with displaying messages with custom styles and icons.
New display settings.
Fixed bugs with displaying messages with custom styles and icons.
New display settings.
Fixed bugs with displaying messages with custom styles and icons.
New display settings.
Fixed an error calling custom JS code when changing pages on the Service Desk portal.
Fixed an error calling custom JS code when changing pages on the Service Desk portal.
Fixed an error calling custom JS code when changing pages on the Service Desk portal.
Fixed an error calling custom JS code when changing pages on the Service Desk portal.
Fixed a bug with incorrect field order
Fixed a bug with incorrect field order
Fixed a bug with incorrect field order
Fixed a bug with incorrect field order
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
UPDATE (29.10.2020):
In this version, there are problems when displaying a message on the portal on the request view screen. Bug fixed in version 4+
UPDATE (29.10.2020):
In this version, there are problems when displaying a message on the portal on the request view screen. Bug fixed in version 4+
All our plugins are developed for Jira Data Center and Server
All our plugins are developed for Jira Data Center and Server
For example, you can configure that a message will be displayed if there are open blocking issues.
"Title" - now you can use HTML for config "Message type" - "Show as is" and "Show as flag" - "No".
Message field and Refined for Jira | Sites & Themes.
In the field configuration, you can specify to whom to display the message - to anonymous users, to all logged-in users or to certain groups or roles.
Bug fixed:
Redesigned message display mechanism. Improved work of JavaScript, fields on the Service desk portal, work on different screens of the issue.
We try to maintain compatibility with previous versions.
For any questions, you can contact support.
Fixed:
Fixed: Selected options in settings are not displayed
Starting with version 2.5.0 you can add a little JavaScript code to your field. With it, you can add a little dynamics to your messages. For example, when creating a issue, display a message depending on the selected fields.
deletes the title of the field and places the message over the entire available width.
.Bug fixed: https://bitbucket.org/jibrok/message-field/issues/5/error-in-html-support.
Previously, the field automatically added <br/> to the message text and formatted some symbols. This was necessary for the correct display of the message.
This approach did not always work correctly. :(
Now any text is saved as is and always displayed as HTML. To move to a new line, you now need to specify <br> yourself.
All messages should be displayed correctly. The only thing, maybe there will be extra characters in them <br/>, you can simply delete them.
Sorry for the inconvenience. If you encounter any problems, please report them in a convenient way.https://marketplace.atlassian.com/apps/1219615/message-field?hosting=server&tab=support
Documentation: https://bitbucket.org/jibrok/message-field/wiki/Script%20Runner%20Behaviours
Released: https://bitbucket.org/jibrok/message-field/issues/4
Hello!
Add new option settings: Show as flag.
Fixed bug: Message field cannot be hided with Script Runner Behaviour Plugin
You can customize the display of a message only in selected statuses.
8.2.1
fix:field error during saving when saving more than 255 chars
Add new custom field type - Message type
Add page for config message with preview.