Bussiness On call route /shifts

[Humberto Gomes]

Hi,

Operations team manager challenges me to be creative and implement a solution for Shifts/On call using JIRA.

At the moment several teams are logging in different tools (Teams, Excel, Outllook, Confluence...).

The idea is to propose a unique solution for all teams.

JIRA is available to all business around so,  can be a good solution... just need the correct format.

Some approaches:

Raise a specific issue type for "Shift" set Shift start date/end date fields, using assignee to define the person.

Show this in JIRA and Confluence Calendar page.

Questions/Challenges

 - Shifts are 1 week per default

 - Should be easy to someone change the current shift, replacing a colleague per 1 day (example). (this must be easy be consulted and HR needs to receive this information for payment purposes.

 - Should we have 1 issue default during 1 week? or 7 issues (1 per day)

 - I have Automation for JIRA app, can help to make part of the manual job.

Brilhant ideias are needed.

Do you have any experience to share?

Note: can't see a plugin to match this. I'm trialing Tempo Timesheets but can't fit my needs.

With a good Business Case we can invest some money in marketplace.

[Daniel Fietta]

Hi @Humberto Gomes,

As you also mentioned "on-call", have you had a look at Opsgenie?

It is only available as a cloud solution but can be linked to your Jira server instance. Raised incidents would reach the right person that is on call and can also be automatically created in Jira.

We would probably need a little bit more information regarding your exact use case(s) but you could have a look at Opsgenie first if that is already what you are looking for.

Daniel
STAGIL

[Humberto Gomes]

Hi,

Many thanks for the sugestion. Opsgenie was alrady tested and it was a NO GO from the majority of stakeholders.

[Daniel Fietta]

Hi @Humberto Gomes

Ok, then you could indeed try the approach of creating a separate issue type "Shift" and use the start and end dates for the planning. One issue per day will probably be too much. Is there a reason why shifts should always have the same length/duration? In case of shift changes ( when someone replaces a colleague), you could adjust the end date, create a new issue for the one day and then another issue for the remaining days of the first employee who got replaced. So the shift issue for that week could have like 3, 1, and 3 days.

With apps like BigPicture, you could visualize those shifts in Gantt charts and have a resource planning tool for those shifts. If you need to include time tracking and planning for those shifts, you can have a look at Tempo Planner as well. 

Daniel
STAGIL

[John Funk]

Hola Humberto,

I don't have a specific experience with something like this but can offer a few suggestions. Others might have better ideas.

I like that you have a specific Issue Type of Shift - that should help. Also, having Automation for Jira should help very much, too. 

In my opinion, if you are going to allow a person to be changed for another person on a day in the middle of the shift, you will probably need an issue per day and not just one per week. 

So, you could create an Epic per week per employee with the custom fields you describe above for shift start and end dates. Then, have Automation for Jira create and link Shift issues for each day in the shift and assign to the employee. 

Then, if a person changes during the week, simply update the assignee to the new person. 

That might be a good start. I don't know what kind of reports that you need on the other end for payment purposes, though. 

Buen suerte!