I'm trying to test the Tempo Planner on a developer instance of JIRA 6.1.1. I can install the plugin, but nothing changes. When I check the add-ons page, it says the plugin is unlicensed. What do I need to do to get it to work? The EAP documentation says a license isn't necessary...
can you inform us if you have Tempo timesheets installed on the same instance? These two plugins are not compatible yet.
Can you inform us also if you get the Tempo link in the header, this is your access to the planner. After install you should have Tempo Planner, Tempo Accounts and the System Plugins Tempo Core and Tempo Teams in your User installed Add-ons list.
A time limited license is included in the .obr file, so you don't need to enter any license. Just ignore that it says "unlicensed".
Please take a look at our documentation https://tempoplugin.jira.com/wiki/display/TP/Tempo+Planner+User%27s+Guide for more information.
Tempo Planner is not yet compatible with Tempo timesheets. You will have problems with running these two plugins as there is a mismatch in some modules. In that case you will need to uninstall all parts of Timesheets and Planner (Timesheets, Planner, Accounts, Teams and Core) and then reinstall timesheets. It is recommended to install Planner in a clean instance of JIRA (useful to have JIRA Agile installed).
Tempo Planner is not yet available in OnDemand, it is still in beta. We are in contact with Atlassian about the release of Planner in OnDemand but do not have any date yet.
Dear Susanne (Tempo Team),
your note above "Tempo Planner is not yet compatible with Tempo timesheets" made me a bit concerned. Is this still the case?
I am asking because we have Tempo timesheets in our production environment and wanted to start testing Tempo Planner.
Is your latest release date at the start of 1Q15 or at the end of it? Meanwhile, are there Tempo Sales Reps available who could do a product overview and answer prospect-specific questions? (The cute cartoons are entertaining, but I'd like to hear about some specific capabilities.) Those would include: * Planning a Program across a joint venture where some parties would have their own Atlassian deployments or would need to work off and online over disconnecting links. (That is, one big central Jira server might not always be available or permitted.) * Ability to hide info from users (even PMs) yet still have access to the skills and availability of a resource (person) for when there are Need-to-Know access limits on projects and people * Ability to schedule Sub-task Due Dates with a Drag-n-Drop UI calendar * Import/Export/Sync with non-Atlassian PM repositories (like MS Project Enterprise repos, Basecamp, TeamworkPM, etc) * Integration with Marketing and CRM services like HubSpot and Salesforce.com
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs