Skip to main content

Fields linked to ‘Time in current’ position

  • August 1, 2023
  • 4 replies
  • 201 views

Fields currently affecting Time in the current position are : 

Job title and Department

4 replies

Hi there,

Is there a way to disconnect some of those fields ?

Currently it means that if we rename a department or move someone to a different department or location but doing the same role, it shows as if they are new to their position.

This impacts performance reporting / visibility as it makes them look as if they are newer to a role than they are.

From my side I would prefer just to link to job title and change type - using the change types identified for promotion or internal mobility.

Any ideas on any work arounds for this?

Thanks

Sharon


Hi ​@Sharon Handy,

 

have you ever found a workaround? We have the same issue.

 

thank you


Hi all,

 

Does anyone know a work around for this? We just had 2 departments that merged into 1 and now it looks like the one that merged into the other only have 1 month of time in role, while their job titles didn’t change. 

 

I’d love to have the same solution as Sharon -  having just a link to job title and change type - using the change types identified for promotion or internal mobility.

 

Has this been raised as a feature request already?

 

Cheers,

Britt


Omri Negbi
Bobber
  • Bobber
  • August 14, 2025

Hi ​@Sharon Handy & ​@Sylvain Chiquot  👋

It is currently not possible to disconnect department or location fields from “Time in current position” tracking in Bob.

Any update, such as renaming a department, moving someone to a new site, or changing their location, will reset the “time in current role” metric, even if the employee’s job title or role responsibilities have not changed.

This issue affects reporting accuracy around tenure in a role and performance visibility.

There is no built-in workaround that lets you link tenure only to the job title and change type (e.g., for promotions or true role changes) while excluding department or location changes.

Multiple users have raised this limitation, but no system-side solution is confirmed.

The only approach mentioned is to manually update and review work history entries, but this does not automate the desired field disconnect or solve reporting impact.