Alendo Apps – License portal
Project Management Assistant Pro – User guide
This guide covers Project Management Assistant Pro (PMA Pro for short) for Jira Data Center, version 0.4 and later. It is made by Alendo Solutions & Services Peter ("Alendo").
PMA Pro is a guided assistant for Jira projects. It helps you change an existing project step by step, or set up a new project cleanly. Everything is pre-filled with sensible values. Whatever other projects share stays protected.
At a glance
- Installation: upload the app file (JAR) via "Manage apps" in Jira.
- Trial: 30 days from the first installation, no key needed.
- License: a license key is valid for one Jira installation (server ID), one user tier and up to an expiry date. You get it from the license portal https://apps.alendo.biz/.
- Offline: PMA Pro checks the license inside your Jira. The plugin does not send any data outside.
- Language: the interface follows each person's Jira language. German users see German, everyone else sees English.
- Support: via a support ticket in the license portal (see Support).
Installation
Which file for which Jira version?
| Your Jira version | File |
|---|---|
| Jira Software / Jira Data Center 11.3 or later | project-management-assistant-pro-<version>.jar |
| Jira Software / Jira Data Center 10.3 (Long Term Support) | [[PLACEHOLDER: file name of the 10.3 build, e.g. project-management-assistant-pro-<version>-jira10.jar, and from which PMA Pro version it is available]] |
| older than 10.3 | not supported |
You can see your Jira version under Administration (cog) → System → System info. Only ever install one of the two files. If you later upgrade Jira from 10.3 to 11.3, upload the 11.3 file afterwards. Settings, runs and license are kept. [[PLACEHOLDER: verify the 10.3 → 11.3 switch against the real 10.3 build]]
Install
- Log in to Jira as an administrator.
- Open Administration (cog) → Manage apps → Manage apps.
- Click Upload app and choose the matching JAR file.
- After installation, the top navigation shows the entry "PMA Pro".
- The settings are under Administration → Apps → PMA Pro – Settings.
The 30-day trial starts now. You don't need a key for it.
Update
Upload the new JAR file the same way as for the installation. Settings, runs, audit log and license key are kept.
Uninstall
Manage apps → Project Management Assistant Pro → Uninstall. Projects, schemes, workflows and everything else the assistant created or changed stay in Jira. Reinstalling does not start a new trial.
License and trial
Trial
- The trial lasts 30 days from the first installation.
- During the trial, everyone who is allowed to can use the assistant in full.
- The assistant shows how many trial days are left. During the last 14 days, the notice is shown as a warning.
- Reinstalling does not reset the trial.
What a license key contains
A key is a block of text that starts with -----BEGIN PMA PRO LICENSE-----. It is valid:
- for one Jira installation, identified by its server ID (looks like
ABCD-1234-EFGH-5678). A cluster with several nodes shares one server ID and needs only one key. - for one user tier, i.e. a maximum number of Jira users. Active users who count against your Jira license are counted, each person once. Up to 10 % more are allowed as a grace margin (example: tier 100 → up to 110 users).
- up to an expiry date (last valid day).
There are commercial licenses and evaluation licenses. Both work the same way; the display says "Evaluation license" or "Commercial license". Prices and user tiers: [[PLACEHOLDER: price list or reference to the quote]].
Finding the server ID
You can find the server ID in two places:
- in PMA Pro under Administration → Apps → PMA Pro – Settings → "License" tab, with a copy button;
- in Jira under Administration → System → System info → "Server ID".
Getting a key (license portal)
The license portal is called "Alendo Apps – License portal" and is at https://apps.alendo.biz/. There are two ways.
You have an invitation by email:
- Open the personal link from the email. It is usually valid for 30 days.
- Enter the server ID of your Jira installation and a contact email.
- Confirm that the server ID belongs to your production Jira installation and click Request license key.
- The key is created, usually within 5 minutes. The page refreshes by itself. You also receive the key by email from the sender
apps@alendo.biz. - Keep the link. You will use the same link later to collect renewals.
You don't have an invitation yet:
- Open https://apps.alendo.biz/ and click Request a license key.
- Fill in the form: product, company, name, email, number of users, type (evaluation or purchase), the server ID if you already know it, and a message.
- You receive a confirmation by email. We review the request and send you an invitation with a personal link. Nothing is issued automatically.
Installing the key
- Open Administration → Apps → PMA Pro – Settings and switch to the "License" tab.
- Paste the whole key into the License key field, including the BEGIN and END lines.
- Click Save key.
PMA Pro checks the key immediately. A key that is invalid, expired or issued for another server ID is not saved. The message tells you why (see Troubleshooting). Only Jira administrators can see and change the "License" tab.
Renewing
Before expiry we send you a quote or an invoice for the renewal [[PLACEHOLDER: confirm the renewal process]]. Afterwards the new key is available under your existing link, and you also receive it by email. The license ID stays the same. Install the new key as described above; it replaces the old one.
PMA Pro shows an "expires soon" notice 14 days before the expiry date.
What happens without a valid license?
After the trial, PMA Pro needs a valid key. If it is missing, invalid, expired, issued for another server ID or for too few users, the assistant is locked for everyone, including Jira administrators: nobody can create or change projects with it.
These keep working:
- Runs that have already started finish, even after a Jira restart.
- Roll back
- the list of runs, the audit log and the policy in the settings
- the "License" tab for installing a new key
Your Jira projects themselves are never affected by the lock. They keep working as usual.
Settings: who may do what?
Jira administrators find the settings under Administration → Apps → PMA Pro – Settings. There are four tabs:
| Tab | Content |
|---|---|
| Policy | who may use the assistant and how far it may go per area |
| Runs | all runs with time, project, type, person and status; administrators can also roll back here |
| Audit log | who started, changed or rolled back what, and when |
| License | status, customer, user tier, expiry, server ID, install or remove the key |
Basic rule
PMA Pro can never do more than the person is allowed to do in Jira anyway. Both their own Jira permissions and the PMA Pro policy always apply, whichever is stricter.
- Jira administrators may always use the assistant.
- Other people need an entry under "Who may use the assistant?" (individual people or groups). The policy levels then apply to them.
- Changing an existing project is allowed for Jira administrators, or for project administrators of that project who are also listed in the policy.
- Creating a new project additionally requires the Jira permission to create projects.
Levels per area
Under "How far may the assistant go?" you set a level per area (e.g. issue types, statuses, fields, screens, permissions). The levels build on each other:
| Level | Meaning |
|---|---|
| Locked – view only | The area is not changed; the default applies. |
| Reuse existing only | People can select an existing scheme or workflow. |
| Copying allowed | People can create a project-specific copy and change it. |
| Creating new allowed | People can create new objects, e.g. statuses, fields or issue types. |
| Changing shared items allowed | People can change schemes or workflows that other projects share. The affected projects are shown first. |
Delegation to project leads (from version 0.5)
From version 0.5, Jira administrators can delegate permissions per project to the project lead or the project admin role. Project leads can then maintain their own project without the Jira administrator having to step in every time. Here too: never more than the person may do in Jira, and never more than the administrator has granted.
[[PLACEHOLDER: describe how delegation works in 0.5 (where in the settings, labels) once 0.5.0 is finished]]
Changing an existing project
This is the most common case and therefore the main entry point.
- Click PMA Pro in the top navigation. Alternatively, open the project's Project settings and click PMA Pro in the sidebar.
- Under "Change an existing project", pick the project. You only see projects you are allowed to change.
- Go through the steps: Basics, Issue types, Statuses & workflow, Fields, Screens, Permissions, Components & versions, Board, Summary.
How it works:
- Everything first shows the current state. You only change what should be different. If you just click "Next", nothing changes; the summary then says "You haven't changed anything".
- Changes are marked as "new", "changed" or "will be removed". Every step can be reset to the current state.
- The summary only shows the differences. Nothing is changed in Jira until you press the start button.
- Shared items stay protected. If other projects use the same scheme, workflow or screen, your project gets its own copy. The other projects stay unchanged.
- No issues are lost. If a status that still contains issues is removed, the assistant asks which status they should move to. Issue types, components and versions that still have issues are not deleted; the assistant tells you what to do first.
You can change: name, description, project lead and category; issue types; statuses and workflow; fields on the screen and their order; screen mapping; permission scheme; roles; components and versions; an additional board. A new project lead is automatically added to the project's admin role.
Creating a new project
- Click PMA Pro at the top and choose "Create a new project".
- Choose the project type (software, business or service) and go through the steps. Everything is pre-filled sensibly. If in doubt, simply click "Next".
- Check the summary and start.
Depending on your choices, the assistant creates its own statuses, workflow, issue types, fields (visible only for this project), screens, a copy of the permission scheme, roles, components, versions, filters and a board – or it reuses existing schemes.
Without Jira Software there are only business projects without a board; the assistant points this out.
During and after a run
- After you start, everything runs in the background with a progress display. It usually takes one to two minutes. You can keep the page open or close it.
- If Jira is restarted in the middle of a run, the run continues by itself afterwards.
- At the end the assistant shows a short list of manual steps that Jira cannot do automatically, e.g. board columns, swimlanes and quick filters. Each item has a link and can be ticked off.
- All runs are listed in the settings under Runs, all actions under Audit log.
Roll back
Every run can be rolled back: directly at the end of the run with "Roll back", or as a Jira administrator in the settings under Runs.
- For a change, PMA Pro restores the previous state of the project: old assignments, removed role members, old project details and the old field order.
- For a newly created project, PMA Pro removes everything the run created, including the project itself with all issues that have been entered in it since. This cannot be undone, so PMA Pro asks first.
Limits of rolling back:
- After a workflow change, issues from a removed status do not necessarily return to their old status.
- A workflow change creates a new workflow. The old one stays inactive in Jira. You can delete it once everything is fine.
- Roll back works even without a valid license.
Known limitations
- The project key and project type cannot be changed.
- Changing fields and choosing a different screen mapping at the same time takes two runs. The assistant explains this in the step.
- Existing boards are not changed. Set up board columns, swimlanes and quick filters manually afterwards (checklist at the end).
- When fields are reordered, a field may move to a different tab of the screen, because the fields are distributed over the existing positions.
- Built-in Jira objects (e.g. the status "In Progress") are shown by PMA Pro with their stored name. Jira itself shows them translated to German-speaking users ("In Arbeit").
- Date fields use the browser's format, not the Jira language.
- License notices only appear in PMA Pro, not as a banner across Jira.
- An issued key cannot be revoked afterwards, because PMA Pro checks offline. It ends on its expiry date.
- Tested on single Jira instances. Not yet tested: clusters with several nodes, very large projects, and a restart in the middle of a workflow migration. [[PLACEHOLDER: update after the tests for 0.5 and the 10.3 build]]
Frequently asked questions
Does PMA Pro send data outside?
No. The license is checked inside your Jira, without an internet connection. Settings, runs and audit log stay in your Jira installation.
Do we need a key to try it?
No. The first 30 days after installation are a trial. If you'd like to test longer, request an evaluation license in the portal.
We have a test and a production instance. Do we need two keys?
Each Jira installation has its own server ID; a key is valid for only one of them. [[PLACEHOLDER: define the rule for test/staging instances, e.g. free second license for a test instance of the same company]]
We are moving to a new server. What happens to the license?
If the Jira database stays the same, the server ID usually stays the same too, and the key remains valid. If the server ID changes (e.g. new database or newly set-up instance), open a support ticket (type "License") with the new server ID. You will receive a new key.
We have more users now.
Up to 10 % above the user tier is covered by the grace margin. Beyond that you need a higher tier; please write to us.
Who can see the license key?
Only Jira administrators, on the "License" tab. The key contains company, license ID, server ID, user tier and expiry date, but no credentials.
Do our projects keep working when the license expires?
Yes. Only the assistant is locked. Everything it created or changed stays and works normally.
Troubleshooting
"The trial period has ended" / assistant locked
The 30-day trial is over and no valid key is installed. Get a key from the license portal and install it under PMA Pro – Settings → License. People without administrator rights should contact their Jira administrator.
"The license key belongs to a different Jira server" / key does not match the server ID
The key was issued for a different server ID.
- Compare the server ID on the "License" tab with the server ID on your portal page or in the "key ready" email.
- Common causes: key installed on the test instance instead of production; typo in the server ID in the portal; Jira was set up again or cloned.
- As long as the key has not been created yet, you can change the server ID on your portal page under "Correct Server ID or email". Otherwise open a support ticket (type "License") with the correct server ID.
"The key is invalid"
- Paste the whole key, including the lines
-----BEGIN PMA PRO LICENSE-----and-----END PMA PRO LICENSE-----. - Ideally copy it with the Copy key button on the portal page. Email programs sometimes add characters or wrap lines.
- A key for another Alendo app is not valid for PMA Pro.
"This key has already expired" / "The license has expired"
The expiry date has passed. Renew the license (see Renewing).
"Too many users for this license"
Jira has more active users than the user tier plus the 10 % grace margin. Deactivate users who are no longer needed or order a higher tier. The key stays saved and becomes valid again as soon as the number fits.
The key does not arrive
- The portal page refreshes by itself; it usually takes up to 5 minutes.
- Check your spam folder for an email from
apps@alendo.biz. - If it still says the key is being created after 15 minutes, open a support ticket.
"This link is invalid or has expired"
Invitation links are usually valid for 30 days. Open a support ticket (type "License") and we'll gladly send you a new one.
The "PMA Pro" entry is missing from the navigation
- Check under Manage apps that the app is installed and enabled and that all modules are active.
- Reload the page (browser cache).
- People without permission only see what they are allowed to use. Check the entry under "Who may use the assistant?".
"The setup didn't work" / "The changes didn't work"
Part of it has already been carried out. Click Roll back and Jira is back to the previous state. Then look for the error in the run's log and send us the details (see Support).
"The rollback didn't fully work"
Some parts could not be removed, e.g. because issues have been added to them in the meantime. The log at the bottom of the page shows which. You can remove them manually or write to us.
Support
- Support ticket: Open a support ticket. You do not need an account. You receive a personal link to the ticket (by email and shown right away). There you see replies and status and reply yourself. We do not read replies by email.
- Lost the link? Under My tickets we send the links to your email address.
- Response time: we reply as quickly as possible. We do not guarantee a fixed response time.
- Please provide (the ticket has its own fields and attachments for this):
- Jira version (Administration → System → System info)
- PMA Pro version (Manage apps)
- server ID and, if available, the license ID (
PMA-…) from the "License" tab - for problems with a run: project key and time from the "Runs" list (or the run ID [[PLACEHOLDER: the run ID is not shown in the interface today – make it visible or drop this item?]])
- a screenshot of the message (PNG or JPG, up to 2 MB) and what you were trying to do
- if you like, an excerpt from the Jira log file
atlassian-jira.logwith lines containingpmapro
We never need the license key itself or any passwords. Please don't send confidential project content.
For general questions not related to an app, contact us at hallo@alendo.ch.
More details: support page
Questions or problems? Open a support ticket · General: hallo@alendo.ch · Alendo Solutions & Services Peter