Unable to create a `jira` team report for mixed logins

[psss]

In the jira plugin self.user.login or self.user.email is used for constructing the search queries. For example:

did/did/plugins/jira.py

Lines 283 to 287 in 27bbcd5

	query = (
	f"creator = '{self.user.login or self.user.email}' "
	f"AND created >= {self.options.since} "
	f"AND created <= {self.options.until}"
	)

In Jira both full email address and just name can be used as login. When defining aliases login and email are autodetected so it's not possible to explicitly specify full email address as a login.

did/did/base.py

Lines 469 to 490 in 98f6593

	# Check for aliases specified in the email string
	if aliases is not None:
	try:
	aliases = dict([
	re.split(r"\s*:\s*", definition, maxsplit=1)
	for definition in re.split(r"\s*;\s*", aliases.strip())])
	except ValueError as exc:
	raise ConfigError(f"Invalid alias definition: '{aliases}'") from exc
	if stats in aliases:
	if "@" in aliases[stats]:
	email = aliases[stats]
	else:
	login = aliases[stats]
	# Update login/email if alias detected
	if email is not None:
	self.email = email
	log.info("Using email alias '%s' for '%s'", email, stats)
	if login is None:
	login = email.split("@")[0]
	if login is not None:
	self.login = login
	log.info("Using login alias '%s' for '%s'", login, stats)

All this together means that it's not possible to create a jira team report if any of the users has email as their login.

Example config file:

[general]
width = 0
email =
    Petr Šplíchal <psplicha@redhat.com>; jira: psplicha@redhat.com,
    Miroslav Vadkerti <mvadkert@redhat.com>; jira: mvadkert

[jira]
type = jira
url = https://issues.redhat.com/
auth_type = token
token_file = ~/.did/jira-token

It would be probably good to allow explicitly define whether login or email is defined by the alias. Perhaps something like this?

email = Petr Šplíchal <psplicha@redhat.com>; jira:login: psplicha@redhat.com

[dkutalek]

Having ability to specify email or login explicitely would be useful for my use case.
I would maybe suggest using jira.login instead of jira:login to make it a bit more readable.

[psss]

I would maybe suggest using jira.login instead of jira:login to make it a bit more readable.

Yeah, that sounds better. I did a quick try with Cursor in #420. @dkutalek, could you please try it?

[dkutalek]

Thank you for quick fix, I quickly reviewed the code, looks good. And it works, too :-)

[dkutalek]

Hmm, I just noticed different behavior when naming the Jira config section [jira] (which works as expected) and differently - eg. with [issues] it does not work as expected. Seems very strange.

[dkutalek]

Ah, got it now - jira.login references name section (as in [jira]), not plugin name. It works if I change both section name and login declaration. Which kind of make sense as eg. different jira instances with different logins can be used. On the other hand, when using same instance in multiple sections eg. for different jira projects - config lines will get long with repeated declarations. Hmm... I can imagine using something like 'plugin.jira.login' or 'section.issues.login' declarations to be it even more flexible, but that goes beyond scope this bug fix.