Frontend: CI/CD catalog: Preserve user page and scroll position
When navigating between index and details page, we should preserve the current page, search, filters and scroll position to make sure the user can resume searching without any slowdowns.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Frédéric Caplette added to epic &9888 (closed)
added to epic &9888 (closed)
- Frédéric Caplette changed the description
Compare with previous version changed the description
- 🤖 GitLab Bot 🤖 added devopsverify sectionci labels
added devopsverify sectionci labels
- Frédéric Caplette added workflowplanning breakdown label
added workflowplanning breakdown label
- Maintainer
Setting label(s) Category:Pipeline Composition based on grouppipeline authoring.
- 🤖 GitLab Bot 🤖 added Category:Pipeline Composition label
added Category:Pipeline Composition label
- Dov Hershkovitch changed milestone to %Backlog
changed milestone to %Backlog
- Frédéric Caplette changed epic to &10917 (closed)
changed epic to &10917 (closed)
- Frédéric Caplette added candidate16.3 label
added candidate16.3 label
- Mark Nuzzo changed title from CI/CD catalog: Preserve user page and scroll position to Frontend: CI/CD catalog: Preserve user page and scroll position
changed title from CI/CD catalog: Preserve user page and scroll position to Frontend: CI/CD catalog: Preserve user page and scroll position
- Mark Nuzzo added candidate16.4 label and removed candidate16.3 label
added candidate16.4 label and removed candidate16.3 label
- Author Maintainer
These issues related to scroll positions tends to be around a weight 3.
Edited by Frédéric Caplette - Frédéric Caplette added workflowready for development label and removed workflowplanning breakdown label
added workflowready for development label and removed workflowplanning breakdown label
- Frédéric Caplette set weight to 3
set weight to 3
- Mark Nuzzo mentioned in issue #421520 (closed)
mentioned in issue #421520 (closed)
- Sunjung Park mentioned in issue gitlab-org/ci-cd/pipeline-authoring#102 (closed)
mentioned in issue gitlab-org/ci-cd/pipeline-authoring#102 (closed)
- Mark Nuzzo added Deliverable label
added Deliverable label
- Mark Nuzzo changed milestone to %16.4
changed milestone to %16.4
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#13702 (closed)
mentioned in issue gitlab-org/quality/triage-reports#13702 (closed)
- Maintainer
Setting health status to
on track
as the milestone has just begun.Issue participants are welcome to override this by setting the health status to another value.
- 🤖 GitLab Bot 🤖 changed health status to on track
changed health status to on track
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#13767 (closed)
mentioned in issue gitlab-org/quality/triage-reports#13767 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#13859 (closed)
mentioned in issue gitlab-org/quality/triage-reports#13859 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#13978 (closed)
mentioned in issue gitlab-org/quality/triage-reports#13978 (closed)
- Maintainer
This issue is scheduled for completion in this milestone but doesn't have an assignee. Changing health status to 'needs attention'.
Issue participants are welcome to override this by setting the health status to another value.
- 🤖 GitLab Bot 🤖 changed health status to needs attention
changed health status to needs attention
- Contributor
Hi @gitlab-com/pipeline-authoring-group/frontend - since this issue was labeled as a Deliverable for %16.4, do we think this will make it or should we prepare for it to move into next milestone? WDYT?
Collapse replies - Author Maintainer
@marknuzzo On my side, given other priorities relating to CI FE health, I will not have capacity to pick this up right now and might do so next week. There is a high likelihood that it will slip
- Contributor
Thanks @f_caplette - as a part of %16.4 close out and carry over, I will update this information accordingly later this week. Thank you!
/cc @dhershkovitch (for visibility regarding frontend planning for %16.5)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14076 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14076 (closed)
- Maintainer
This issue is scheduled for completion in this milestone but doesn't have an assignee. Changing health status to 'at risk'.
Issue participants are welcome to override this by setting the health status to another value.
- 🤖 GitLab Bot 🤖 changed health status to at risk
changed health status to at risk
- Dov Hershkovitch changed milestone to %16.5
changed milestone to %16.5
- Dov Hershkovitch removed health status at risk
removed health status at risk
- Mark Nuzzo removed Deliverable label
removed Deliverable label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14145 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14145 (closed)
- Dov Hershkovitch changed milestone to %Backlog
changed milestone to %Backlog
- Dov Hershkovitch added candidate16.6 label and removed candidate16.4 label
added candidate16.6 label and removed candidate16.4 label
- Dov Hershkovitch mentioned in issue #394818 (closed)
mentioned in issue #394818 (closed)
- Fabio Pitino mentioned in issue #427868 (closed)
mentioned in issue #427868 (closed)
- Contributor
Hi @f_caplette - was this a part of your showcase you did recently or was I mistaken? Do you think this is doable in %16.6 with the other frontend work? Is this something that is critical for Global Catalog Beta? WDYT?
/cc @jreporter
Collapse replies - Author Maintainer
@marknuzzo It has not been included but it is not critical to Beta. It is merely a nice to have here.
1 1
- Mark Nuzzo removed candidate16.6 label
removed candidate16.6 label
- Sunjung Park changed epic to &11902
changed epic to &11902
- Mark Nuzzo added VerifyP3 label
added VerifyP3 label
- Dov Hershkovitch added gitlab-org#15241 as parent epic
added gitlab-org#15241 as parent epic