You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
See attached screenshot below. Note that I can create tickets with JIRA portal just fine. I only see this issue while trying to do so with Capture for JIRA extension.
1) I'm trying this from a new machine so right from Chrome and the JIRA extension everything is freshly installed. The Capture for JIRA extension for example is installed today.
2) Logging out and logging back in did not fix the issue.
3) Restarting Chrome did not fix this issue either.
4) I can't see any field called "Reporter" to be able to edit that.
Can someone look into this and let me know if I've missed something?
|Google Chrome||62.0.3202.89 (Official Build) (64-bit)|
|OS||Mac OS X|
How is configured this field in Jira? Check also the permission scheme just in case.
There actually hasn't been any change with the permission scheme to have caused this issue for me.
However, it is only today that I'm seeing this issue. My colleagues don't see any issues while creating tickets either, with both JIRA portal and the extension.
However, I changed something on JIRA portal which potentially resolved this issue for me now.
Steps I followed:
1) On the JIRA portal, Click on + button to create Issue
2) Go to Configure fields
3) Check the checkbox for "Linked issues"
I didn't have to make any changes anywhere else. You may mark this question as answered. Thanks for your help!!
Glad you resolved it.
It is you who have to mark the accepted solution, I guess you can make a new comment and check it as resolved
@Gary Kosman I'm assuming you're getting the error when you are trying to create the issue in freshdesk?
If so, I discovered that the problem was that I wasn't using the username as it's listed in JIRA. It took me awhile, but the only way I could find my actual username that worked was to go into JIRA > Settings > User Management > Export Users and you should see a column for username.