As far as I know - nope :) But the feature should be there.

I'm not a great fan of this feature.

At JWC Deb Nicholson spoke about the problem of "licking cookies" and I've observed this a lot in our project. Someone "claims" an issue and then no one else will touch it and due to time constraints etc the person never works on it or does so slowly.

If we are to have this feature then there should be an automatic reset of the assignment after a period of inactivity.
You may blame the J!Tracker Application for transmitting this comment.

Yes, I watched Deb speak about though I can't say I've actually experienced and serious incident like that. That said, I can't fault the reasoning but I will want it for the Framework and probably the whole distribution scene. If the CMS chosen not to have it for their tracker that's fine - they just ignore it. Also, I'm looking at using this for Github Enterprise at work so this is important to me (and if I can do that, I can justify work time helping out).

Bottom line is I'm probably prepared to shoulder the feature, I just couldn't see an foundation work for it.

I think you and I are both experience (hard nosed) enough to ignore people "licking cookies" but I can show hundreds of issues in the cms where progress has been stopped by "experienced" people licking the cookie and then not following up.

Having said that I can also see your need for this feature so while I would say no to it for the CMS tracker I would be perfectly OK with it being an option for any other tracker using this code.
You may blame the J!Tracker Application for transmitting this comment.

I'm fine with that. I didn't really have the CMS tracker itself in mind when asking the question. If it was used in the CMS, I could see it used amongst the merge team once a PR has passed all user and automated testing.

I think it was somewhat "abused" in the CMS tracker so, not a top priority but yes, I think we should implement this definitely in version 2.

Not yet.