Product Version: NetBeans IDE Dev (Build cdev-340-on-090310)
Java: 1.5.0_16; Java HotSpot(TM) Client VM 1.5.0_16-133
System: Mac OS X version 10.5.6 running on i386; MacRoman; en_US (nb)
Description of the scenario:
-user is in Kenai dashboard and clicks on "Find Issue..." related to his Product XYZ
-imagine that the product XYZ has only 3 bugs (#123, #124, #125)
-the user can type issue number (e.g. "1") into the Issue ID textfield of the Find Issue page
-when pushes 'Go To Issue' button the details of bug #1 are displayed
-->> Although the issue #1 belongs to different Product that the current one the issue is displayed. Only issues from
the context of current product should be reachable. There is a question whether this should be handled on the side of
server (I don't know whether it is possible to set up bugzilla somehow for this purpose) or should there be some hack on
the side of IDE?
reassigning to xdesign
ondra, do you think in makes sense to block issues which don't belong to the actual project
alternative solution would be to show only a warning that the requested issue does not belong to the project
It is generally unavoidable, you can access issues from other projects, if not in the IDE then in the browser, given the
way how Bugzilla on Kenai is done (mixed numbering across all projects). So I think the IDE should not try to block
issues from other projects. It's important the query page offers the right 'product', but otherwise if the user types in
an issue ID that exists, then why not to show it. I don't think it does any harm, it definitely does not prevent the
user to do anything the right way.
I suggest won't fix.
I tend to agree with the reporter, if user accesses the dialog from a Kenai project and the "issue tracker" clearly
describes current project as context, only issues belonging to that project should be allowed to access.
But I can think of a one (not too likely use-case) when this would do some harm - when user mistypes the issue number,
he will end up in (and possibly editing if hot-headed) a wrong issue. In this case, he should probably be warned ... or
given a message that there is such issue on given project.
But in fact, the priority is IMO very low ... in most situations this really does no harm. Agree on wontfix if not
Tomas, please let me know how difficult you think this would be. I'll either close as wontfix or suggest a particular
don't think the fix (warning or error msg) would be a big deal. It's only that we won't know to which project the issue
belongs until we load it's data from the repository and speaking for myself - i tend more to the point tpavek made in
his last post - "why not to show it" if we already have the issue on the client. Maybe a warning would be better then
simply blocking the user and forcing him to open find issues for the right project and invoking goto issue again.
Something like "Hey! issue XXX doesn't belong to project YYY. Do you want to open it anyway? [ ] don't show this warning
I agree with the warning .. dialog box should do ..
Integrated into 'main-golden', will be available in build *201003040200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Tomas Stupka <email@example.com>
Issue #159988 - Only bugs related to selected Product should be available