Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,637
Community Members
 
Community Events
176
Community Groups

How Does Workfront Plugin Determine Reporter?

Hi - we've installed the Workfront Plugin for Jira Server and created a few triggers. We've created a service account and authenticated the plugin via the service account. The issue successfully gets created in Jira after being created in Workfront, however my account keeps getting tagged as the reporter. Has anyone experienced this or have any ideas? I would think the reporter would match whoever the reporter in Workfront is.

1 answer

Was there by chance ever an answer to this?  I'm having the same issue

Also having exact same issue. Set up as described in original question, using a system account to Workfront, but when things come back into Jira (both new issues and comments), shows as the user who originally installed the Workfront add-on (me).  I tried creating a system account on the Jira side with the same email as the Workfront system account, no change.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events