backstage / backstage/community-plugins
π ServiceNow: Incidents / tickets table improvements
- Dominant language
- TypeScript
- Stars
- 422
- Forks
- 697
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 286
Description
### 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](https://developer.servicenow.com/dev.do#!/learn/learning-plans/washingtondc/new_to_servicenow/app_store_learnv2_buildmyfirstapp_washingtondc_personal_developer_instances).
2. Installed and configured the ServiceNow plugin and got this:
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:
```tsx
import { themes, UnifiedThemeProvider } from '@backstage/theme';
import { EntityServicenowContent as _EntityServicenowContent } from './EntityServicenowContent';
export const EntityServicenowContent = () => {
return (
<_EntityServicenowContent />
);
};
```
And started my experiments with
```bash
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?
- [x] I checked and didn't find similar issue
### π’ Have you read the Code of Conduct?
- [x] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)
### Are you willing to submit PR?
Yes I am willing to submit a PR!
Contributor guide
Research direction
Start with plugins/servicenow/src/components/Servicenow/index.tsx and follow EntityServicenowContent into the incidents or tickets table implementation. Review the table's data-loading and display configuration, using the linked ServiceNow experiments to reproduce the current ordering and status filtering. Done means newest tickets appear first and resolved or closed tickets are excluded by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100