Issues marked as Done still appears in a New Sprint

[Marco_Santiago]

We configured our workflow so that we have have a status of Deployed (for code that has been successfully tested and deployed). This status is mapped to a category of Done in the status definition screen. We also have status of a Closed in the workflow, for issues that are resolved for other than deployed status. This status is also mapped to a category of Done.

The problem that we're having is that when we set the status for an issue to Deployed, we're expecting these issues to drop off when we create a new sprint since these issues were resolved from the previews sprint. 

How do we get this to work?

[Nic Brough -Adaptavist- · Accepted solution]

There's no way to do this with the standard email handlers.  They are working on the basic assumption that the sender of the email is a JIRA user who can create issues, but the emails are not being sent by an email address it can recognise.  JoeSmith has an email address of domain.com, not domainalias.com.

Some options might be:

1. Dummy accounts (ugly because Joe would have two accounts)
2. Find/write a new handler
3. Install an email proxy with a rewrite in it

Unfortunately, I don't think options 2 and 3 can be done on Cloud.

[Brian Latimer]

That, unfortunately, makes sense.  Thanks for the insights.

[Andy Brook]

Brian, how /where is the 'true source' of user registration, do you have an LDAP server somewhere?  Potentially this is something we can add to JEMHC (Enterprise Mail Handler for JIRA cloud), we already have the same solution with JEMH (for JIRA server), the example here is when a user with an account in ActiveDirectory sends from a different address that is aliased to the same user, JEMH can hen query LDAP and assert the correct user is in context

• https://thepluginpeople.atlassian.net/wiki/display/JEMH/Use+LDAP+to+create+users#UseLDAPtocreateusers-ExampleAlternateIDlookup

Doing that for cloud is possible, but we haven't hit this scenario in cloud yet.

[Brian Latimer]

Thanks, Andy!  I don't believe we're using an internal LDAP server - just using Google logins for account tracking, and handling the domain alias.  I like the idea of JEMH … but don't think we'll be able to move off of the cloud, at least for the time being.

In investigating further, I found https://jira.atlassian.com/browse/JRA-3160 … which would obviously handle this situation quite nicely - as well as allowing for messages personal email addresses to all be recognized as being from the same user account.  I'm dismayed to see that it appears this is not to be addressed, however.