This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Right now when I login, the website takes me to my account page. It should instead return me back to the page I loged in from and let me continue what I was doing. Very often, I want to just go in and report a bug but I can't do so without having to pass through my personal account page. The login/password text panels on the left should be replaced with a link to the account page. Furthermore, I would _really_ appreciate it if you could give me the option of leaving a cookie on my computer so I don't have to re-login every single time I visit the website.
1) The first point - "after login should go back to page I came from", is a valid issue. Collab please note I don't think this is the same as issue 13568, "login should process bug/should not be able to edit bugs without login". 2) Gili - why should the user/pwd panels be relaced ? I don't understand this comment here ... ? 3) cookies are used, always have been, though there are/have been problems with them. See issue 13479. This part is a duplicate. Assigning to support for point 1).
I think for point 2 what I meant to say is that once you login, the part of the panel on the left that used to belong to "username/password" should now include a link to your account-home.
OK, that makes sense - however that has always been the behaviour of the navbar, the txtboxes are replaced with "My Start PAge" ... :-/ So, only open issue here is part 1), assigned to Collab.
*** This issue has been marked as a duplicate of 13568 ***
Taska, please see my note above : -- 1) The first point - "after login should go back to page I came from", is a valid issue. Collab please note I don't think this is the same as issue 13568, "login should process bug/should not be able to edit bugs without login". -- 13568 is about not being able to edit a bug when not logged in. As I understand it Marek is working to either add some txt to the IZ page about that, or to disable the COMMIT button. 14050 (this issue) is about staying on the current page when logging in, ie returning to whatever you were doing rather than going straight to MyStartPage. I don't think these are duplicates. Perhaps this is an enhancement rather than a defect though ...
Okay, I assumed that we were tracking this information in issue 13568. We already have an internal issue for this (PCN5345), targeted for the SC1.3 milestone.
i'm surprised this is considered an enhancement. this is a defect. moreover, it is a regression from the pre-sourcecast days when logging it would return you to what you were doing (entering a bug). by rights, it should be a p2. the fact that we have to live with the current way of working for two more releases of sc is very frustrating...
Our engineers are definitely looking at this actively (new issue number: PCN6139). I can move this to DEFECT if you want.
Our engineers have moved this internally to the SC1.3.1 milestone.
Oops, I should call that the 1.3 milestone. The third decimal is not yet certain.
*** Issue 22488 has been marked as a duplicate of this issue. ***
Administrative Change; SC1.3 has been renamed SC2.0.
Can you give me the delivery date for SC 2.0 ??
I cannot provide an exact date when SC 2.0 will be released, but we are looking at later this year.
This has been fixed in SourceCast 2.0. During the upgrade to that release we can verify or reopen if necessary.
Reopened, because I'm still getting the old result. Please, close only when the actual upgrade is done.
Maxym, the upgrade to SourceCast 2.0 was not done yet. Collabnet Support claims it's fixed and we will verify that on staging server when it will be available.
*** Issue 51336 has been marked as a duplicate of this issue. ***
When are we moving to SourceCast 2.0?
We should move to 2.6 within a few months, though of course that could slip.
Updating...
Looks like this didn't actually get fixed in 2.0 ?
*** Issue 61206 has been marked as a duplicate of this issue. ***
Ping. Yet another issue supposedly fixed in a new release but wasn't, and nobody noticed bcs the issue was closed ?
Any news?
Doesn't look like this is working as requested. Looking into this.
This is trully really annoying :/ Fix it, PLZ 100+ votes to fix this.
I updated Issue 18462. This issue will get resolved along with that. The 2 issues are actually stemming from the same root cause; hence marking this as a duplicate. *** This issue has been marked as a duplicate of 18462 ***
Still not fixed. Reopening, un-duplicating. See issue 18462 for details.
This is fixed via a patch(it couldn't make it before the site upgrade); we should have this patch on the site in a few weeks.
Can someone please verify if this is now correctly working on the stage.netbeans.org (since we have put in some changes). If it is satisfactory, I will roll-out this change to production.
Any feedback on this issue?
Wow yes it really works! I visited http://www.stage.netbeans.org/issues/show_bug.cgi?id=14050, and used the login form in the top nav. I wound up on the same issue page, but logged in! This is excellent, thanks!
If you go to the homepage then click REPORT A BUG, and log in, it'll take you to a different page than had you already been logged in and hit REPORT A BUG. I'd expect a consistent behavior.
NOTE: This issue is addressed in the stage site; not yet rolled out in production. Here are the steps I followed: 1. Start as a logged out user on the stage.netbeans.org site. 2. Go to http://www.stage.netbeans.org/community/issues.html 3. Select http://www.stage.netbeans.org/issues/enter_bug.cgi [Enter a New Issue] 4. Takes me to http://www.stage.netbeans.org/issues/enter_bug.cgi (Permission denied) 5. I enter my username, password on the top right login boxes. 6. I still stay on http://www.stage.netbeans.org/issues/enter_bug.cgi [Enter Issue page] as logged in user. Also, I tried various other pages. Should anyone else encounter any issue, please provide detailed step-by-step instruction, including URLs from the stage site.
What Gili reports is not related to this issue. It is a trivial link issue - we can address that when the fix is rolled out to the live site. The original issue here is fixed on the stage site.
OK, we will schedule this roll out on the production site in the next couple of days. This particular branding change will not require any site restarts.
This is now fixed on production.
Verified - this is great, thanks. Gili, the issue you mentioned is now fixed also.
We recently moved out from Collabnet's infrastructure