Page MenuHomePhabricator

Redirect back to task after log in to phabricator (using the link in the right top corner)
Closed, ResolvedPublic

Description

Upstream report: https://secure.phabricator.com/T6870

When I click on a task link from an email I will land on the task. Usually than I need to log in to work with the task. But clicking the log in link in the right top corner does not bring me back to the task after succesfully log in.

This feature in MediaWiki is very helpful and we should have it also in ourer task tracker, bugzilla was also redirecting after log in.

It works when using the "Login to Comment" at the bottom of the page, but I do not want scroll down before log in, because I have do it a second time after log in.

Would be nice when this gets added to phabricator. Thanks.

Event Timeline

Umherirrender raised the priority of this task from to Medium.
Umherirrender updated the task description. (Show Details)
Umherirrender added a project: Phabricator.
Umherirrender changed Security from none to None.
Umherirrender added a subscriber: Umherirrender.
Qgil lowered the priority of this task from Medium to Lowest.Nov 28 2014, 10:23 AM
Qgil edited projects, added Phabricator (Upstream); removed Phabricator.
Qgil added subscribers: chasemp, Qgil.

This task has been resolved upstream: https://secure.phabricator.com/T6870

I don't know whether this fix will be available with T78243: Phabricator upgrade on 2015-01-14 or whether we have already picked a snapshot for the next upgrade. @chasemp, can you help answering this, please?

In T76202#964786, @Qgil wrote:

This task has been resolved upstream: https://secure.phabricator.com/T6870

I don't know whether this fix will be available with T78243: Phabricator upgrade on 2015-01-14 or whether we have already picked a snapshot for the next upgrade. @chasemp, can you help answering this, please?

@mmodell and @Christopher were going to settle on a common version, I'm not sure yet where that is in relation

Qgil claimed this task.

It's not fixed in the version we just deployed. The fix will come in the next one, then.