Hello, I am trying to create a gadget for jira, in which I want to show the time required tempo, that service should utlilizar, I added this dependency:
<groupId> com.tempoplugin </ groupId>
<artifactId> tempo-core </ artifactId>
<version> 2.0.7 </ version>
<scope> provided </ scope>
Would I would serve with this? that service would have to rely for the time required.
I am not exactly sure what you want to accomplish with this gadget. Maybe you can explain that better. There is currently no public java API in Tempo to do this, you can browse the available REST services in Tempo through the REST API browser but I don't think they will provide everything you need. This sounds like something Tempo could offer. I suggest you file a feature request here: https://tempoplugin.jira.com/.
exactly what I need, is to get the planned and Requiered times to display associated with each worker (apart from other data that are not tempo), are very similar gadget that provides tempo (capture). But no use to us, because we want to show a lot more data.
I managed to get time Required as follows:
userScheduleManager.getRequiredSeconds (user, Pair.of (LocalDate, LocalDate));
but I lack the time planned, is there any way you could get by user
Thank you, Regards
As you have managed to figure out, Required workload can be found by using the UserScheduleManager (however this isn't a public API, and we make no promises to support those methods in the future, so you use them at your own risk).
As of Tempo 7.9 (due in about two weeks) the plans from Tempo Timesheets and Tempo Planner will be available using the AllocationService in the Tempo Planning API plugin (tempo-plan-core). The same warning applies here (not officially public, nor supported and you might have to do some digging around to figure out how to get exactly what you need.)
Getting the actual hours worked, might prove more difficult. Tempo Timesheets doesn't offer an API for that.
I encorage you to create a new feature request (http://tempoplugin.jira.com) and ask us to make publicly available these three stable API's: Required, Planned, Worked. I am sure it would be looked favourably upon.
I am using the below code but it does not even recognize AccountService Interface from com.tempoplugin.account.service
My plugin works fine without instantiating AccountService
When I remove the code for getting accounts and just instantiate the AccountService my plugin fails with a 404
Are the Java API's for Tempo not PUBLIC?
My java code and pom are as below
REST CLIENT CODE
public Response getProjects(@Context HttpServletRequest request)
String username = userManager.getRemoteUsername(request);
ApplicationUser user = userUtil.getUserByName(username);
User dirUser = user.getDirectoryUser();
Collection<TempoRepresentation> tempoRepresentations = new LinkedList<TempoRepresentation>();
List<Account> accounts = accountService.getAccounts(dirUser);
for (Account account : accounts)
TemposRepresentation allAccounts = new TemposRepresentation(tempoRepresentations);
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
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