Issue Collector: is it possible to determine if user is logged in to Jira?

Grzegorz Korba October 5, 2015

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:

  • Client application configures default values for name/email fields
  • Those values are used in form fields for not logged in users
  • Real credentials are used when user is logged in, default values are omitted

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.

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
GabrielleJ
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 6, 2015

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.

Grzegorz Korba October 6, 2015

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 ;-)

TAGS
AUG Leaders

Atlassian Community Events