Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Help -> Report Bug or Enhancement is effectively useless #338

Closed
merks opened this issue Dec 12, 2023 · 14 comments
Closed

The Help -> Report Bug or Enhancement is effectively useless #338

merks opened this issue Dec 12, 2023 · 14 comments
Milestone

Comments

@merks
Copy link
Contributor

merks commented Dec 12, 2023

It's empty:

image

so not only kind of unless, it creates a bad impression:

https://www.eclipse.org/forums/index.php/mv/msg/1114126/1862577/#msg_1862577

@merks merks changed the title The Help -> Report Bug or Enhancement is effectively uselss The Help -> Report Bug or Enhancement is effectively useless Dec 12, 2023
@ruspl-afed ruspl-afed added this to the 4.2.0 milestone Dec 20, 2023
@nitind
Copy link

nitind commented Jan 8, 2024

Perhaps the relevant UI contribution shouldn't enable unless a provider is installed?

@BeckerFrank
Copy link
Contributor

@merks , @nitind : Currently there is only one provider in org.eclipse.mylyn.bugzilla.ide (see the definition of the extension point in plugin.xml).
The way this is implemented allows us to disable the action if no providers are defined. But this code is called too late, so you have to select the action and then get an information dialog with the text "The chosen operation is not enabled". Is this a better solution?

@merks
Copy link
Contributor Author

merks commented Jan 10, 2024

Anything that's in the menu and looks inviting but then is useless is probably going to make people shake their heads...

@BeckerFrank
Copy link
Contributor

Anything that's in the menu and looks inviting but then is useless is probably going to make people shake their heads...

This is only useless as long as you not install the Bugzilla feature. In the plugin.xml are the following Products defines
Bildschirmfoto 2024-01-10 um 18 09 42
If you select one you end up with a new Bugzilla Ticket and prefilled some fields.

Should we

  • remove this complete
  • add a similar function to GitHub and later GitLab connector if possible

@ruspl-afed
Copy link
Contributor

There should be a special table item "Install more providers... ", acting as a launcher for install action

@merks
Copy link
Contributor Author

merks commented Jan 10, 2024

@jonahgraham Given bugzilla at eclipse is on the way out, we should not have the in packages if it typically useless.

@jonahgraham
Copy link
Contributor

+1 to removing it - I will create a bug to review and figure out how to remove from EPP if it is still there later in the release cycle. eclipse-packaging/packages#102

FWIW it is equally as dated as the Help -> Contribute that directs to https://www.eclipse.org/contribute/ which is mostly simply dated. eclipse-packaging/packages#103

@ruspl-afed
Copy link
Contributor

Why bugzilla outage should be a reason to remove this functionality at all? Let's reroute it to GitHub and GitLab where Eclipse projects are hosted now, as suggested by @BeckerFrank above.

@merks
Copy link
Contributor Author

merks commented Jan 11, 2024

We only mention that because the comment was that bugzilla was the only provider. If there is GitHub/GitLab that would be helpful!

@mjmeijer
Copy link
Contributor

mjmeijer commented Jan 11, 2024

From memory when I was contributing to Mylyn more actively:
User Story/Case:
Any plugin can define an extension point (have to look up which one) that specifies the bug/issue tracker where tickets/bugs can be opened. Then when said plugin dumps an error in the Error Log, selecting the error and selecting the context menu should allow one to report the log message and some extra information as a bug in the appropriate issue tracker, auto-checking for duplicates first. Hence the stacktrace search as that is deemed a sufficiently unique identifier of the error.

The Goal was/is to make it easier for people to report issues and allow a more data driven approach to bug fix prioritization.
This scaffolding provided by the Mylyn ecosystem with the example implementations should be retained in my view.
This provides tremendous time savings for testers and early adopters of new software in the Mylyn ecosystem.
Hope I can find the time to dig in the old docs and do a write up.

As intermediaire solution:
Remove from Help menu, retain UI in ErrorLog context menu and update code to point to new issue trackers.
Add functionality to GitHub and GitLab issue trackers

ruspl-afed added a commit that referenced this issue Jan 31, 2024
Reroute Mylyn, Platform and PDE from Bugzilla to GitHub
ruspl-afed added a commit that referenced this issue Jan 31, 2024
Reroute Mylyn, Platform and PDE from Bugzilla to GitHub
@ruspl-afed
Copy link
Contributor

@jonahgraham I did a reroute for Mylyn, Platform and PDE from Bugzilla to GitHub and this is a part of Mylyn 4.2.0 M2 contribution to SimRel.
Perhaps it can commute the sentence from EPP side.

@jonahgraham
Copy link
Contributor

Perhaps it can commute the sentence from EPP side.

Yes! and wonderful. eclipse-packaging/packages#102

@ruspl-afed
Copy link
Contributor

Thank you @jonahgraham for verification!
Please note, that for GitHub we have only these Eclipse Projects where I have committer role and know for sure how to submit an issue. Others require additional investigation to understand the status of migration from Bugzilla.

I hope we can close this one @merks and open others for particular Eclipse Project to appear in the wizard.

@merks
Copy link
Contributor Author

merks commented Feb 1, 2024

Great job. 👏🏿

@merks merks closed this as completed Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants