Versions Compared

Key

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

...

After opening any of queued requests, whilst being logged-in, as any user with Vacation Manager access granted, since 2.2.x version of the add-on you can spot additional elements marked with (A) and (B) and named as "sections" here to provide additional information:

Image RemovedImage Added

(info) The above-presented image, shows a vacation request as seen by an HR member group (because of full edition possibility of such request and explanation of all possible to see elements within).

...

  • "Labels" (1) - Its content can be added/removed only by requesting user and HR team members. User's LM is unable to edit it. When content is editable, you can spot blue pencil icon . Upon accessing it you should see a similar view as presented below:
    Image RemovedImage Added
    It's possible to use existing labels, or type here a new name and new label will be placed.

...

If you tick "Send Notification" an email is to be send to all involved parties (which are in the presented case: leave requesting user and his line manager, by a person from HR who has added new label). As presented below, such delivered email contains information about ticket update and adding a label to a leave request (marked green):

Image Removed Image RemovedImage Added Image Added

(info) Prior SMTP server configuration in Jira is needed to make it work properly. Check here.

When label gets created and is present within the request, upon clicking on it, new Jira search is to launch and display all issues labeled like that (i.e. "April_and_May" - to quickly find leaves that are in April in May, given that label had been used to tag leaves with such dates prior to this):

Image RemovedImage Added

  • "Period Type" and "Used vacation days" are a non-editable informative only fields and refer to selected leave type and factual number of requested off-work days from its assigned total quota (excluding weekends and other bank holidays).
  • "Teams" (2) - in terms of its creation and behavior, this field is an equivalent of "Labels" and in fact it uses labeling method.  Likewise "Labels", can be edited by requesting user and HR Team members only. What differentiates it from "Labels is that when leave request is created, this field automatically gets filled with a name the same as leave requesting user's team (i.e. like in the above presented example - "Team_1").

...