Hi Rohit,
welcome to the Atlassian Community.
This usually happens when the user’s profile gets its name data from an identity source or an integrated account (for example Atlassian Guard.).
Opsgenie will automatically use the display name that comes from that linked Atlassian user profile, and sometimes it can appear truncated if the sync doesn’t process correctly.
Here are a few steps to check:
- Go to admin.atlassian.com → Directory → Users and verify that the Atlassian account for Audumbar Nikam has the correct full name.
- If the name looks fine there, try removing and re-adding the user in Opsgenie. This triggers a resync of the display name.
- Clear browser cache or try in an incognito session. Sometimes cached directory data shows an outdated name.
If the problem still occurs after those checks, it might be a data sync bug. In that case, it’s best to open a support ticket with Atlassian Support under the Opsgenie product area and include the affected user’s email for investigation.
Hope this helps you get it fixed quickly!
One more important note: Atlassian has announced that Opsgenie will reach end of support in the future and that customers are expected to migrate to either Jira Service Management (for full ITSM and incident management) or Compass (for DevOps-centric alerting and service catalog), depending on their use case. It is therefore a good time to start thinking about your long-term target platform so that any configuration work you do now (including users and naming conventions) aligns with your migration path. A helpful starting point for structuring this is Atlassian’s general cloud migration planning page at Migration Plan .
If this resolves your issue, feel free to mark the answer as accepted so others with the same problem can find it more easily.
Greetings,
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.