Skip to content

🐛 ServiceNow: Incidents / tickets table improvements #5267

@christoph-jerolimov

Description

@christoph-jerolimov

Workspace

servicenow

📜 Description

I have some opinionated suggestions for the incidents / tickets table:

👍 Expected behavior

  1. Latest tickets should be shown on top
  2. Resolved or closed tickets should be ignored by default

👎 Actual Behavior with Screenshots

  1. The table shows the oldest tickets first
  2. And it shows also all the resolved and closed tickets

👟 Reproduction steps

  1. I've created a test instance via the ServiceNow Developer Portal.
  2. Installed and configured the ServiceNow plugin and got this:
Image

My experiments are available here:

  1. https://github.com/christoph-jerolimov/backstage-experiments/tree/main/servicenow
  2. https://github.com/christoph-jerolimov/backstage-experiments/tree/main/servicenow-nfs

I changed plugins/servicenow/src/components/Servicenow/index.tsx to:

import { themes, UnifiedThemeProvider } from '@backstage/theme';

import { EntityServicenowContent as _EntityServicenowContent } from './EntityServicenowContent';

export const EntityServicenowContent = () => {
  return (
    <div>
      <UnifiedThemeProvider theme={themes.dark}>
        <_EntityServicenowContent />
      </UnifiedThemeProvider>
    </div>
  );
};

And started my experiments with

yarn start --link ~/git/backstage/community-plugins/workspaces/servicenow

📃 Provide the context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

Yes I am willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions