gitlab issues menu

[Thausand]

Is some thing change for use issue when use fpc gitlab ?

There not more exist menu plan->issues and now is name plan->workitems and have other/new interface.

I have read documentation gitlab and not mention for change for workitem, fpc wiki not mention change for workitem so then not know how is use workitem. Now is more work for navigate and/or report issue.

Is change for future or is gitlab have problem with configure ?

[Martin_fr]

We don't decide the Gitlab updates, that is done by them. We are just using the platform "as provided". So no idea.

I still see an "Issues" item unde "plan" => though when creating a new issue there is a choice, and issues/work-items can be accessed under different urls, but both are avail for both url.
Maybe if you are viewing an "issue" that happens to be a work item...

Also in the past there were options to preview next beta, don't remember where to toggle.

[n7800]

I saw the new interface the day before yesterday.

But only now have I noticed that it's not activated in some projects. Lazarus still has the old interface, while FPC (replacing "work_items" in the link to "issues" will still perform a redirect) has the new one. Is anyone else seeing the same thing?

The new interface has a feedback button that leads to this page. I asked a question there about the feature's deployment.

[n7800]

Now is more work for navigate and/or report issue.

I haven't really used the new interface yet, but I don't see any major issues compared to the old one. Instead of clicking the "Open"/"Closed" tabs, I can click the word "Open" in filter to select another option.

The report creation button are still the same, in the same place. So for regular users, the change is really more a matter of renaming "issues">>"work items".

The only truly ugly thing is the URL change. But I'm afraid there's nothing I can do about it anyway ((

Overall, it's more like the GitHub interface (example), although it still retains the "Open"/"Closed" tabs, which creates ambiguity, since this information is also present in the filter...

In any case, all feedback should be directed to the GitLab team, as the FPC developers won't do anything about it: https://gitlab.com/gitlab-org/gitlab/-/work_items/590689