Release Manager

Inspiration

Releasing products to production, dev or any environment requires steps, documents and most of all tickets.

What it does

The responsibility of this application will be to give the user the ability to:

1) Create Documents need for a release that could range from update an system to installation, however, since this is beta version, idea is to get an installation document created

2) Manage tickets once they are submitted by anyone, requires time and patiences. ServiceNow is the only way to review what your tickets status once you submitted. Most of the time it requires the user login, plugged in the number, get the thru all the info to see what approval is needed. For example, as a Boarding Team member we would like to know the status and state of the ticket. What approvers are needed and what documents are missing. Sometimes the servicenow emails get lost in an endless amount of incoming emails that the team member will miss the update.

How I built it

With the use of C# and REST API, I would attempt accomplish this project in-order to centralized the need info to focus on projects and release. But also keep a third eye on ticket status, approvers/rejections.

Challenges I ran into

Accomplishments that I'm proud of

What I learned

What's next for Release Manager

Built With

• c#
• rest
• rest-api