Here is how an administrator can set up Plutora from scratch.
First Login
When you log into Plutora for the first time, you will be the only user and your account will be set up as an administrator, so you will have full access to Plutora.
It is recommended that you update your password when you log into Plutora for the first time.
You can enable SSO with Login Settings. You can also add your company logo.
Set Up Users
Add User Roles
Give your users the permissions that they need to work.
Add Organizations
Companies consist of departments, branches, workgroups, or individuals. These are represented as the Organization Structure.
Set Up User Custom Fields and Lists (Optional)
Plutora has fields for the name, email, phone number, and location of each user. If you would like to record more information, create User Custom Fields. If one or more of those custom fields is a drop-down menu or combo box, add items to those custom fields using User Custom Lists.
Add Site Messages
Your new users will need to know what their first steps should be and how to ask for help. Add a Login Page Message or an Announcement Feed to give them this information.
Add Users
Once your user roles, organizations, and user custom fields and lists are ready, you can start adding users and User Groups.
Set Up Systems and Environments
Once you have set up users, you can start setting up Environments.
Set Up System and Environment Customizations
To make Plutora’s Environments your own:
- Add your own statuses, such as Active, Decommissioned, or N/A, or just use the ones already set up.
- Add your own phases, such as UAT, Production, or Development.
- Will you be using Environment Technical Specs and Configuration? If so, you need to add Stack Layers.
- Go above and beyond the available fields with:
- Environment Custom Fields and Lists.
- Environment Group Custom Fields and Lists.
- System Custom Fields and Lists.
- Customize the connector arrows in the Environment Map.
Add Systems
Add some Systems. Systems must be added before Environments.
Add Environment Groups
Add some Environment Groups.
Add Environments
Now that your mandatory fields, Systems, and Environment Groups are set up, you can start adding Environments.
Set Up Releases and Changes
Set Up Release and Change Customizations
To make Plutora’s Releases your own:
- Customize the default Enterprise, Project, and Independent Release Titles.
- Add your own Release and Change Statuses, such as Draft, In Progress, or Completed. If you use Jira, match them to the statuses in Jira.
- Add your own Release Types, such as Minor or Major.
- Enable Release intake approval in Release Intake Status so you can approve child Releases added to parent Enterprise Releases.
- Name your Release Phases and Gates.
- Go above and beyond the available fields with:
- Release Custom Fields and Lists
- Change Custom Fields and Lists (if you use Jira, match its fields).
- If you plan to use Insights Dashboard, set up:
- Insight Management
- Phase/Gate View
- Release Type Group View
- Actions – View By Type
- Widgets Title.
Changes
Add some Changes, which are often used to bring in stories or tasks from ServiceNow or Jira.
Releases
Add Enterprise, Project, and Independent Releases.
Add Activities and Criteria to their Phases and Gates.
Deployment Plans
Get started with Deployment Plans.
Blockout Periods
If you plan to use Release Calendar, add Blockout Periods to represent your holidays and other special events.
Use Environments with Releases
Set Up Environment Request Customizations
To make Plutora’s Environment Requests your own:
- Add TECR (Test Environment Change Request) and TEBR (Test Environment Booking Request) statuses so you can create workflows.
- Give your TECRs and TEBRs types.
- Go above and beyond the available fields with:
- Give your users instructions on how to add TEBRs and get them to answer questions about the booking with TEBR Form.
- Choose which TEBR fields are mandatory.
- Create TEBR Time Slots to make it easier to book an Environment for just a few hours instead of all day.
TEBRs
A Test Environment Booking Request (TEBR) is a form that is used to book an Environment or Environment Group. Users can book one or many Environments or Environment Groups in a single form. Booking requests can be associated with Releases or created as placeholder bookings without Releases.
TECRs
A Test Environment Change Request (TECR) is a form that is used to make changes to an Environment or Environment Group, such as a code deployment, or an infrastructure change. Like a TEBR, one or many Environments or Environment Groups can be linked into a single form.
Environment Bookings
Book Environments directly from Enterprise, Project, and Independent Releases.
View, Export, and Report on Data
Email Templates
Use Email Template Wizard to create email notifications.
To create email templates quickly, try copying and customizing the default templates. Remember to target emails to the people who need them, so that people who don’t need them aren’t spammed.
Integrations
Retrieve, create, update, and delete records using Plutora’s API.
Establish customized integration layers between systems using Integration Hub – API.
Integrate Plutora with Jira, ServiceNow, Jenkins, and Github.
Plutora Analytics
Use Plutora’s powerful report center.
Insights
Insights Dashboard provides a one-stop view of Release, Test, and Quality data.
Release Schedule
View a timeline of your Releases.
Environment Schedule
Find and fix conflicting Environment Bookings.
Systems Impact Matrix
Systems Impact Matrix shows how Releases impact or pose a regression risk to Systems.
Environments Impact Matrix
Environments Impact Matrix gives users a graphical view of bookings and shows whether they are Approved, Pending or Rejected against Releases.
Release Calendar
View and filter your Releases, Blockout Periods, TEBRs, and TECRs by date.
Need Support?
Search the knowledge base or contact Support.