Release 7.1 Notes

At a Glance

• New, more flexible resource role and rate management
• Introduction of Open API (Phase 1)
• Improved Jira integration (direct import)
• Updated SharePoint integration (modern authentication)
• General performance and technical improvements

---

Key Enhancements

1. Resource Roles & Rates – Major Upgrade

This is the biggest change in the release.

We’ve completely reworked how roles, rates and resource assignments are managed to give you more flexibility and better historical tracking.

---

What’s changed?

Dedicated tabs for clarity

Both Roles and Resource Details screens now include structured tabs:

• Details
• Rates
• Skills
• (Resources also include Roles and Leave)

This makes it much easier to navigate and manage information.

---

Time-based Rates (NEW)

Rates are now time-bound, meaning you can define different rates for different periods.

What this means for you:

• Set future rate changes in advance
• Keep a full history of previous rates
• Avoid overwriting old data

Good to know:

• Existing rates have been migrated automatically
• Historic rates are hidden by default (use Show Past to view them)
• Rates cannot overlap and must be valid positive values

---

Time-based Role Assignments (NEW)

Resources can now be assigned to roles with start and end dates.

What this means for you:

• Track how roles change over time
• Align roles with rate changes
• Improve reporting accuracy

---

Inherited vs Override Rates

Rates now work in three layers:

1. Role Rates (default)
2. Resource Override Rates
3. Plan/Project Override Rates

How it works:

• Resources inherit rates from their role
• You can override rates at resource level
• You can override again at plan level

Priority order:
Plan rate → Resource rate → Role rate

---

New Plan-Level Rate Management

You can now manage project-specific rates directly within a plan:

Plan > Resources > Resource Rates

What this means for you:

• Adjust rates for specific projects without changing global settings
• Better financial control at plan level

Permissions:

• Only Plan Owners, Admins or Resource Managers can edit
• Others have read-only access

---

Open API (Phase 1)

We’ve introduced the first version of the PM3 Open API.

What it does:

• Allows external systems to create plans automatically
• Populate key fields on the Plan Details page

Why it matters:

• Reduces manual data entry
• Enables integration with other systems
• Lays the foundation for future automation

This is just the start — more API capabilities will follow in future releases.

---

SharePoint Integration Update

The SharePoint integration has been upgraded to use Microsoft Graph API.

Why this change?
Microsoft is moving away from Basic Authentication, which many clients are now disabling.

What this means for you:

• More secure and future-proof integration
• Continued connectivity with SharePoint
• Alignment with Microsoft best practices

Action required:

• Configure a new Azure App registration
• Update settings in PM3 under Admin > General

---

Jira Integration – Now Much Simpler

You can now import Jira data directly into PM3 — no more spreadsheets.

New Process (4 steps)

• Create an API token in Jira
• Add credentials in PM3 Admin
• Link a Jira project to your plan
• Import data via the Product Backlog
  
  

What this means for you:

• Faster setup
• No manual file handling
• Cleaner, more reliable data import

Important:

• This is a read-only, one-way sync
• Imported data will be overwritten on re-sync
• Changes should be made in Jira, not PM3

Additional Improvements:

• General performance enhancements
• Technical improvements across the platform

What You Need To Do:

Depending on your setup:

• Resource Managers: Review new rate and role functionality
• Admins: Update SharePoint integration (if applicable)
• Jira Users: Start using the new direct import feature
• All Users: Familiarise yourself with the updated layouts

---

PM3BI