Flyspray Tracker Management

[rgleason]

Original OpenCPN Bug & Feature Request Management
Flyspray Tracker

April 25, 2021
Simplified, renamed and reduced Tracker "Projects" in an effort to eventually close it completely.

1. Moved OpenCPN beta and release older than v5 into "inactive" status. (also renamed for consistency)
2. Moved all empty pi-[Plugin] projects into "inactive" status.
3. There are now about 37 "inactive" projects (many with the original tasks and bug/feature requests) that can be reactivated.
4. Deleted a couple of unused projects.
5. Cleaned out some old tasks (older than 2019) for a few specific "projects" and deleted those very few projects.
6. Renamed things more consistently.
7. There are still a considerable number of projects that need closing.

Goals

1. All plugin bugs and feature requests posted in respective github repository..
2. All OpenCPN bugs and feature requests posted in OpenCPN github repository.

Questions:

1. When to "Turn off" or "Disable" portions of Tracker?
2. Should we allow users to continue to post bug and feature requests to Tracker?
3. When should we change all website and wiki links for Bugs and Feature Requests.
4. Do we expect all users to get github accounts so they can file bugs and feature requests?
5. What to do about many existing bugs and feature requests in Tracker?

Next Immediate Steps? @bdbcat

• Close & Remove all bugs and feature requests earlier than 2019 (2018 Cleanup)?
• Then request OP to review and close the remaining if it is no longer current?
• Feature Requests (200 now)
  -- Present-2019 (50 open) Keep and ask OP if still relevant, if not please close.
  -- 2018-2010 (150 open) Simply Close as part of "2018 Cleanup" ?
  -- Labeled bug (16 open) (If they really are bugs move to Opencpn Bugs current version?-
• Please advise.

[rgleason]

@bdbcat

Rather than

• "Close & Remove all bugs and feature requests earlier than 2019 (2018 Cleanup)?"

I can move all of those entries into

• "00 Feature Request earlier than 2019"
  and then make that project "inactive"
  If you can give me bulk rights.

[rgleason]

@bdbcat

Dave, you are right, I looked all over and there is no Bulk enable. The message that pops up says:

"Sorry, bulk editing is currently disabled for Flyspray 1.0. We plan to finish implementation for a later release of Flyspray. You can enable them in source code again at your own risk, but read the comments there before doing it."
There is a reason it is not enabled, so perhaps we could upgrade Flyspray to enable bulk operations? There is a message towards the top

Please update Flyspray. Your current version is 1.0-rc4 and the latest version is 1.0-rc9 . (remind me later)
http://www.flyspray.org/docs/download/
I think this version would do it
https://github.com/Flyspray/flyspray/releases/tag/v1.0-rc8

• move task to other project now handles all cases (1.0-rc7 was quite strict to reveal possibe inconsistencies to the user, but incomplete to provide solutions)
• mass operation can now be enabled in admin area. But no check for possible inconsistencies and no notifications will be sent for that operations!
• minimum PHP5.4 (older PHP5.3 may work, but not tested anymore) - PHP7.3

This would really help clean up Flyspray. Then we can figure out what to do next with "Feature Requests".
I assume you want all OpenCPN bug and feature requests to be put in Github Issues?

• So Users will need a github account.

  BTW Dokuwiki has moved from flyspray to Github issues and their flyspray is no longer available.

[rgleason]

I have tried to move some of the Feature Requests prior to 2019 into "Feature Request Earlier than 2019" and it requires 12 clicks for each and every item, doing it individually.

We need a faster and better way of doing this and updating flyspray would work
https://github.com/Flyspray/flyspray/releases/tag/v1.0-rc8 requires minimum PHP 5.4 to 7.3