ITSM Banners

Get Started
Default and Current Configuration ( simple - for POC )
(Optional) Setting Project for Global Banners
We got you covered - no need to search through projects
Global and Project Banner
Global Banner
Use of Admin section for Global Banner
Global and Project config on app queue page

Inspiration

Our own support experience and the drive to boost productivity.

What It Does

Saves time (and reduces frustration) by improving communication with customer portal users through banners.
One-to-many communication saves effort, and anticipating user needs creates happier customers!

How We Built It

With Forge!
With Love!
With Coffee!

Challenges We Faced

Architecture: Everything seems simple at first, but the details can be tricky. However, asking the right questions and narrowing decisions makes everything manageable.
AI Completions: Models trained on outdated data were often stubborn, defaulting to @forge/ui or <TextField>. While helpful, relying on AI sometimes led to hours of debugging.
Time Allocation: We spent too much time deliberating over challenges instead of building iteratively in small, manageable steps.

Accomplishments We're Proud Of

Creating a MultilineText component that supports line breaks!
Setting up a configuration system for both global and project-level settings—it was no easy task!
Delivering a simple, clean, and visually appealing app.

What We Learned

React props are awesome.
Forge documentation is excellent.
Having a strong knowledge base is crucial.
Don’t rely too heavily on AI.
Always use Git!

What's Next for ITSM Banners

For the MVP:

Refactoring, refactoring, refactoring.
Updating documentation.
Releasing to the Marketplace (target: end of 2024).

Planned Improvements:

Audit log implementation.
Introducing banner lifecycles (draft, active, inactive, deleted, archived).
Auto-scheduling capabilities.
Event-based banners.
More granular scopes, e.g., issue/request types, organizations, anonymous users, etc.