Versions Compared

Old Version 9

changes.mady.by.user Bogdan Neacsu (Unlicensed)

Saved on

compared with

New Version 10

changes.mady.by.user Radu Dumitriu (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can make your Jira fields do basically anything at any point of time, just add and set up Live Fields configuration and associate it with a project.

...

  1. Log into your Jira as Admin.
  2. Go to Administration > Add-ons > Live Fields.
  3. To add a live fields configuration, click Add Live Fields.


     
  4. In the dialog box, fill out the necessary fields:
    1. Enter the configuration name and description.
    2. Select a SIL ™ file for the live fields configuration. This is a SIL script that will be executed on every issue page for the associated projects.
    3. Select the necessary projects or project categories to associate with the configuration.
      Since v 4.6, you also have to select one or more Application Environments to run the script into. Example: "Jira Core" or "Service Desk Customer Portal".
       

You can edit and remove a configuration by clicking the Edit/Delete icon on the Live Fields configuration page.


Info
titleWait! Only one configuration per project or category ?

Yes, and it was a design decision we had to take. The motivation for this is very simple, it all boils down to performance and predictability.

  1. Launching an interpretor is a complicated task, which we want to avoid doing multiple times, especially when you have to react as fast as possible because you need to hide some fields on the screen
  2. Imagine you have 2 scripts. Script 1 hides a field, script 2 shows the same field. Sometimes script 1 terminates faster than script 2, sometimes is the other way around. Leaving aside that you would probably have to coordinate this from the client, how do you apply them? Imposing an order would be the same as writing just one script.

We therefore believe that one script is enough;  you can use includes to share behavior between different configurations.

Info
titlePrecedence in applying LiveFields

Note that a Project LF configuration takes precedence over a Project Category LF configuration, if they happen to overlap.


See also

Live Fields Routines

...