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

• JQL condition - in the field settings, you can set a JQL condition. If the issue matches the specified search query, the message will be displayed.
• $permissionHelper - In dynamic templates, you can check the rights(project permissions) of the current user or the user specified in the issue fields.

• JQL condition - in the field settings, you can set a JQL condition. If the issue matches the specified search query, the message will be displayed.
• $permissionHelper - In dynamic templates, you can check the rights(project permissions) of the current user or the user specified in the issue fields.

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.

Example in documentation.

• locale - A Locale object represents a specific geographical, political, or cultural region of currentUser.
• language - Returns the country/region code of currentUser.
• country - Returns the country code of currentUser.

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.

Example in documentation.

• locale - A Locale object represents a specific geographical, political, or cultural region of currentUser.
• language - Returns the country/region code of currentUser.
• country - Returns the country code of currentUser.

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:

• $currentDateTime
  • The current date time.
• $dateOfLastTransition
  • The date of the last transition.
• $secAfterLastTransition
  • How many seconds have passed since the last transition.
• $previousStatusId
  • Number ID of previous status.
• $previousStatusName
  • Name of previous status.
• $transitionId
  • Number of current transition.
  • Only available on transition screens.
• $transitionName
  • Name of current transition.
  • Only available on transition screens.

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:

• $currentDateTime
  • The current date time.
• $dateOfLastTransition
  • The date of the last transition.
• $secAfterLastTransition
  • How many seconds have passed since the last transition.
• $previousStatusId
  • Number ID of previous status.
• $previousStatusName
  • Name of previous status.
• $transitionId
  • Number of current transition.
  • Only available on transition screens.
• $transitionName
  • Name of current transition.
  • Only available on transition screens.

• Fixed: default message value gets into email (technical information)
  • A new option has been added to the field settings.
  • Show only on create screens: No/Yes
  • Additional customization for creation screens.
  • Technically prohibits displaying messages outside of compose screens(Issue create screen, Service desc create screen).
  • After creating a issue, some versions of Jira or third-party applications may ask for the default value of the field if there is no data in the issue. This option prevents the field from being returned after a request has been created.
  • The setting works at a low level. Tech messages still show up in frontends, third party plugins or email - please write to support.
• Other minor fixes
• You can use the message to display any other fields on the Service Desk portal and in requests.
  • Example in documentation:
    • https://jibrok.com/docs/message-field/dynamic-templates-examples/ -> How to show fields from linked issues(also on Service Desk Portal)? How to use $issueFieldRender?

• Fixed: default message value gets into email (technical information)
  • A new option has been added to the field settings.
  • Show only on create screens: No/Yes
  • Additional customization for creation screens.
  • Technically prohibits displaying messages outside of compose screens(Issue create screen, Service desc create screen).
  • After creating a issue, some versions of Jira or third-party applications may ask for the default value of the field if there is no data in the issue. This option prevents the field from being returned after a request has been created.
  • The setting works at a low level. Tech messages still show up in frontends, third party plugins or email - please write to support.
• Other minor fixes
• You can use the message to display any other fields on the Service Desk portal and in requests.
  • Example in documentation:
    • https://jibrok.com/docs/message-field/dynamic-templates-examples/ -> How to show fields from linked issues(also on Service Desk Portal)? How to use $issueFieldRender?

Fixed bugs with displaying messages with custom styles and icons.

New display settings.

• Message
  • View: show field name. Other: show field name.
  • View: show field name. Other: hide field name.
  • View: show field name. Other: hide field name and left aligned.
  • View: hide field name and left aligned. Other: show field name.
  • View: hide field name and left aligned. Other: hide field name.
  • View: hide field name and left aligned. Other: hide field name and left aligned.
  • View screen: hide field name. Other screens: show field name.
  • View screen: hide field name. Other screens: hide field name.
  • View screen: hide field name. Other screens: hide field name and left aligned.
• Flag
  • Small pop-up in the upper right corner.
  • Big pop-up

Fixed bugs with displaying messages with custom styles and icons.

New display settings.

• Message
  • View: show field name. Other: show field name.
  • View: show field name. Other: hide field name.
  • View: show field name. Other: hide field name and left aligned.
  • View: hide field name and left aligned. Other: show field name.
  • View: hide field name and left aligned. Other: hide field name.
  • View: hide field name and left aligned. Other: hide field name and left aligned.
  • View screen: hide field name. Other screens: show field name.
  • View screen: hide field name. Other screens: hide field name.
  • View screen: hide field name. Other screens: hide field name and left aligned.
• Flag
  • Small pop-up in the upper right corner.
  • Big pop-up

Fixed bugs with displaying messages with custom styles and icons.

New display settings.

• Message
  • View: show field name. Other: show field name.
  • View: show field name. Other: hide field name.
  • View: show field name. Other: hide field name and left aligned.
  • View: hide field name and left aligned. Other: show field name.
  • View: hide field name and left aligned. Other: hide field name.
  • View: hide field name and left aligned. Other: hide field name and left aligned.
  • View screen: hide field name. Other screens: show field name.
  • View screen: hide field name. Other screens: hide field name.
  • View screen: hide field name. Other screens: hide field name and left aligned.
• Flag
  • Small pop-up in the upper right corner.
  • Big pop-up

Fixed bugs with displaying messages with custom styles and icons.

New display settings.

• Message
  • View: show field name. Other: show field name.
  • View: show field name. Other: hide field name.
  • View: show field name. Other: hide field name and left aligned.
  • View: hide field name and left aligned. Other: show field name.
  • View: hide field name and left aligned. Other: hide field name.
  • View: hide field name and left aligned. Other: hide field name and left aligned.
  • View screen: hide field name. Other screens: show field name.
  • View screen: hide field name. Other screens: hide field name.
  • View screen: hide field name. Other screens: hide field name and left aligned.
• Flag
  • Small pop-up in the upper right corner.
  • Big pop-up:

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.

• Minor fixes and improvements
• Now you can configure in more detail who to show the message to. The statuses, groups and roles for which to show the message and for which to hide it are configured separately.

• Minor fixes and improvements
• Now you can configure in more detail who to show the message to. The statuses, groups and roles for which to show the message and for which to hide it are configured separately.

• Minor fixes and improvements
• Now you can configure in more detail who to show the message to. The statuses, groups and roles for which to show the message and for which to hide it are configured separately.

• Minor fixes and improvements
• Now you can configure in more detail who to show the message to. The statuses, groups and roles for which to show the message and for which to hide it are configured separately.

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:

• NPE error in the field settings.
• Display on the portal for users with restricted rights in Jira.
• Improved the operation of field contexts.

Fixed:

• NPE error in the field settings.
• Display on the portal for users with restricted rights in Jira.
• Improved the operation of field contexts.

Fixed:

• NPE error in the field settings.
• Display on the portal for users with restricted rights in Jira.
• Improved the operation of field contexts.

Fixed:

• NPE error in the field settings.
• Display on the portal for users with restricted rights in Jira.
• Improved the operation of field contexts.

• This field is available for export
• The display settings are also applied for export Printable

• This field is available for export
• The display settings are also applied for export Printable

• This field is available for export
• The display settings are also applied for export Printable

• This field is available for export
• The display settings are also applied for export Printable

Fixed:

• The message was not always displayed on transitions

Fixed:

• The message was not always displayed on transitions

Fixed:

• The message was not always displayed on transitions

Fixed:

• The message was not always displayed on transitions

• You can customize the color of your messages in detail without using HTML - documentation
• Work with Clone Plus for Jira

• You can customize the color of your messages in detail without using HTML - documentation
• Work with Clone Plus for Jira

• New website with documentation and examples.
• New message rendering mode - Dynamic templates. It allows you to change the message on screens in real time without using JavaScript or Script Runner.
• Custom colours
• Rest services for exporting and importing settings.
• Improved display of messages on the Service Desk portal.
• Banners are displayed in the JQL navigator and when printing issue.
• Administrator interfaces are improved.
• New interface for viewing all available fields in the system.
• Support Clone+

Contact us for any questions.

• New website with documentation and examples.
• New message rendering mode - Dynamic templates. It allows you to change the message on screens in real time without using JavaScript or Script Runner.
• Custom colours
• Rest services for exporting and importing settings.
• Improved display of messages on the Service Desk portal.
• Banners are displayed in the JQL navigator and when printing issue.
• Administrator interfaces are improved.
• New interface for viewing all available fields in the system.
• Support Clone+

Contact us for any questions.

• New website with documentation and examples.
• New message rendering mode - Dynamic templates. It allows you to change the message on screens in real time without using JavaScript or Script Runner.
• Rest services for exporting and importing settings.
• Improved display of messages on the Service Desk portal.
• Banners are displayed in the JQL navigator and when printing issue.
• Administrator interfaces are improved.
• New interface for viewing all available fields in the system.

Contact us for any questions.

• New website with documentation and examples.
• New message rendering mode - Dynamic templates. It allows you to change the message on screens in real time without using JavaScript or Script Runner.
• Rest services for exporting and importing settings.
• Improved display of messages on the Service Desk portal.
• Banners are displayed in the JQL navigator and when printing issue.
• Administrator interfaces are improved.
• New interface for viewing all available fields in the system.

Contact us for any questions.

• Fixed displaying messages on the portal after the first login.

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+

• Fixed displaying messages on the portal after the first login.

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

• REST for plugin and field configs - documentation
• Fixed for 3.2.3
  • Messages are updated immediately when the Behavior script is executed, if the result is received before the timeout.
  • Configuring Javascript execution before or after Behavior.

• Show the message only if there are links to other issues. In the field Settings, you can specify the link types and statuses of related issues. If the original task has the appropriate links or corresponding related tasks, the message will be displayed.

  • For example, you can configure that a message will be displayed if there are open blocking issues.

• The field settings page has been slightly improved.
• When setting the timeout, you can configure whether to show the original message before executing the script from Scriptrunner.
• Improved work with the Service Desk portal. All field settings now work on the portal as well.

"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.

Documentation

• improved flag operation on all issue screens.

• improved flag operation on creation, editing and transition screens (Jira Core).
• improved flag operation on Jira Service Desk portal.

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.

Documentation

Bug fixed:

• message not showing on some screens.

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 JavaScript code, you will need to set contexts in the field settings.
• It is recommended to check custom JavaScript and ScriptRunner behavior scripts.

For any questions, you can contact support.

• Improved work on the Service Desk portal.
• Improved integration with ScriptRunner and JavaScript api plugin.
• Added a new display option - Big flag - displays a message in a popup.
• Added contexts to display the message itself. This is necessary in case you use only 1 screen, but for example, the message should be displayed only when created.
• Added code editor.

Fixed:

• Bug - don't display message on create screen
• Disable field for bulk operations

• New message type - "Show as is". It type shows just title and body. You can custom message body with html.
• Remove change log for message field

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.

• Message field work on the portal Service Desk. "SR Behaviors" also works (Beta).
• New view mode in the field settings. Standard and Big. The size of the displayed message on the issue view screen. Big -

  deletes the title of the field and places the message over the entire available width.

  .

• New message type "Change" for Jira 8.4.0+

• Bug fixed - Duplicate a message on a view screen: https://bitbucket.org/jibrok/message-field/issues/6/message-visualization-loops-in-view-screen

• Bug fixed - Not correct restore text field value from config

Bug fixed: https://bitbucket.org/jibrok/message-field/issues/5/error-in-html-support.

• In version 2.3.0+, the field displays any message only as HTML.

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.

• Important!

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

• setHidden
• setFormValue text
• setFormValue JSON

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.

Field appear/disappear

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.