(In reply to Johan Lorenzo [:jlorenzo] from comment #2) > 2. It opened a new Taskcluster tab (on the Firefox CI instance), which Sylvestre ignored because to him, he's just dealing with Treeherder. He didn't close the tab, he just went to Treehreder The next deployment of Taskcluster UI will instruct the user to sign in to provide TC credentials to Treeherder. However, if the Taskcluster UI tab is ignored, then the user won't know. In that case, we could probably do something from the Treeherder side. > 3. On Treeherder, there was no message saying it's waiting to hear back from Taskcluster, instead it showed the error showed on comment 0. The Treeherder UI could probably show a notification message when a user tries to login or when TC credentials are expired to instruct the user to complete the credential fetching flow. sclement, thoughts?
Bug 1597205 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Johan Lorenzo [:jlorenzo] from comment #2) > 2. It opened a new Taskcluster tab (on the Firefox CI instance), which Sylvestre ignored because to him, he's just dealing with Treeherder. He didn't close the tab, he just went to Treehreder The next deployment of Taskcluster UI will instruct the user to sign in to provide TC credentials to Treeherder. However, if the Taskcluster UI tab is ignored, then the user won't know. In that case, we could probably do something from the Treeherder side. > 3. On Treeherder, there was no message saying it's waiting to hear back from Taskcluster, instead it showed the error showed on comment 0. The Treeherder UI could probably show a notification message when a user tries to login or when TC credentials are expired to instruct the user to complete the credential fetching flow. sclements, thoughts?