I am wondering if user's credentials could be determined (or at least if user is logged in or not) while configuring issue collector on client's side.
In our case the problem is that if we set default values for name/email fields (in IC configuration) but user is logged in, those values overrides real user's credentials, so we lose some more reliable data.
Desired behaviour:
If we knew user is logged in we could omit setting fieldValues.fullname and fieldValues.email and it would fix the problem.
Edit: I've reported an issue, but I'm still looking for workaround.
Community moderators have prevented the ability to post new answers.
Yes, the JIRA issue collector will determine if the browser has a cookie (determines if the user is logged-in on JIRA in the same console) then it will display the data. The problem if it's not. There is a feature to add "username" and "email" to be required, but right now they are not even custom fields in JIRA, they are just being appended in the issue description.
I know it all, the problem is different. When user is determined (is logged in), but collector is configured with default name/email fields' values, those values are used to set issue's reporter. I want to determine if user is logged in BEFORE setting default values, so reporter would be real Jira's user. There are 2 solutions: - Determining user before configuring collector on the client's side - Fixing Jira so it will not override user's session credentials with name/email sent from the collector I can't fix Jira, so I want to determine user ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.