Page History

hello and welcome everybody to this tutorial today so today we are going to look into the ultimate set-up guide for temple for jira so my name here today on the line is Alexander AG and I'm working as a senior product expert with temple so I want to be sure that this tutorial today is headed for temple administrators mainly and and I would also point out that you should have quite good journalist because I'm also looking into some chamber parts of two parts of JIRA so that's because the temple is very tight - JIRA as well when it comes to permissions and I want to it at rest of course mainly new Tempe users but that's this session might also be useful for existing Tempe users when it comes to know where if they need to know if or if you want to need to know if you've got covered everything and if you have set up everything in that way like it should be so everything that I'm going to do here today is based on some kind of best practices guidance and but of course it's it's not a must like like I do things here or that I'm going to do things here today there are many customers out there that set up maybe temple in a different way I just want to make sure that that you have everything covered and I will get you through a process that will basically bring it to to the minimal or to the basic setup for temple to get started as soon as possible so however I'm going to focus myself or all the presentation on tempo timesheets because the demo that I'm going to do here today is we're temple timesheets only but I will also cover some aspects that are related to tempo planning so specifically when it comes up to when we set up teams and so so but I will try to point it out during the presentation just for you to know that I'm not specifically point out a planner here but I will also for sure mention that in some cases that also relate to temple planner so what I'm going to do here today so a little bit of of the agenda here today so first of all I'm going to do demo here based on GRA 8 so it's I'm going to everything that I do here today is based on the GRS server version however in this slide or two slides later I will also live with point out what is different between temple cloud woods or temple for forever server so there of course and slight differences I want to point that out a little bit in the beginning but also do the presentation I might point out some points that are not available in cloud or vice versa so that also depends a little bit so we I will start with the settings in JIRA so there are some settings that you need to know or that you should should be aware of I would go into global permission permission schemes custom fears and also JIRA groups a little bit and and then I will spend the most of the time into the configuration of temple in general this includes the user meant user management and tempo how you set up workload and holidays games we will look into tier roads teams and I will also set up a basic set of accounts we will look into gadgets very roughly two I will I will show you where you can find or how you can find temple cats gets that are available for temple and how you can place them into your dashboards for you for you users and I will also point you to some guidance on integrations or how you can get started or to point you to some guidance on integrations or external reporting with the temple but they will also be is or a separate webinar next week which is that developer guide where I'm going to into those details in in word or into into that matter in more detail so and like I said it is it is I'm going to look into some of best practices here during this session here today and so not very specifically but in each one single item I will probably point out some of those best practices that you should do but you of course can also do things differently that's that's for sure and at the end I'm going to look into your questions of course so I told you that I'm going to look at half a demo here which is based on your server however you have also a version for your cloud available and you might ask or I will just want to point out what's what's different here so in very general the approach is the same everything that I'm going to present you today is the same on CMS server and cloud so that's very jungle of course so they might of course some differences between cloud and server so specifically when it comes to two permissions there's one specific permission setting in in the JIRA protect Commission screen which is the view is yours and this is for example quite important when it comes to setup the configurations and the permissions in Temple so we can of course look into that a little bit later on when there are some questions related to that but otherwise I just wanted to point out here that these are different permissions another thing that I'm want to point out is that the cost rates are only supported for JIRA server version and I'm also looking to today how you can basically manage your stuff and this feature is only available for server however it's it's only in UI or it's making things easier for you however all the possibilities is also available and cloud for of course but manage staff section that I'm going to look into it today is making things easier for you makes it easier for you to to set up your temple instance so and then we also have different reports between the hosting environment so there are some reports that available server on but not on cloud but some and and vice versa so there are some slight differences for you to know we are developing at the moment the quite lot of reports and and we are a little bit different or going in two different directions depending on the hosting environment here so so but however I'm not going to cover that in specifically and in general I'm very much based on the back end here today it basically means I'm not going into very much detail and how you really lock your time or how you how you create reports there are different or other webinars that are occurring this features okay so I also want to point out I'm not going to do that specifically on this weapon here today but it is very important for you to know that we have a mobile app both for server and cloud so it's not the same app there are two different applications or two two different apps available on their marketplaces for Apple and Google so watch out for those apps they are highly they're highly rated so makes it really easy for your users to to track the time with our mobile app so check that out and make sure that you also have that on your radar somewhere okay maybe one final slide about resources we also talked about a little bit of resources specially when it comes to to temple planner and people also of course within temple timesheets talk about the capacity or the required requirement of hours of your team members so all this is we can all this set this up in tempo so when I talk for a compass for example for a team it is nothing else than a collection of JIRA users very similar what you do with groups but in different terms but I will also come later in here today why and how we should set up teams but like I said for very Java it's for you to know what a team is and when we also talked about capacity or a team member capacity that is calculated from the ROC lot and the holiday scheme that I will also show you here in a couple of minutes how this is done and how this is set up so but let's get started so closing these slides here so what I'm going to have here today the presentation today is a very very much I just want to lock out as this person here is a is a quite new JIRA installation so I do not have very much or basically I have everything set up from scratch so the only thing that I have is one JIRA project that I just created from zero a sample project and I have two projects but I will come to that a little later so you basically see here that I have two projects one one is the project here that I had created from a sample a sample project from JIRA and another one is internal one but I will let me show you how and why I did that exactly but I told you that I'm going to start with JIRA section so first of all I'm going to start in the manage tab section and from here maybe very short very quick I want to point out that I have se prophecy as temple timesheets installed here so this is the only thing that I have did in this instance otherwise it's really it's a really clean instance and what you need to know is once you install tempo timesheets or tempo planner or a temple budget of one of our other add-ons you all get these system plugins installed as well so these are subheadings from temple so once when you whenever experience some differences or problems with tempo timesheets and the amount to dissin uninstall temple time City and install again make sure you also uninstall all the system plugins because they are shipped with a temple as well don't worry about that all the data that is behind all the plugins still will still remain in tempo so whenever whatever whenever you install the temple plugins the data that already has been set up will still remain in the database okay so once I have Temple times its installed I will see a lot of other things that are be injected into JIRA behind the scenes and this is something that I'm going to point out but before I go there I want to go to the user management from JIRA and I will tell you why so this little bit depends on what this is a little bit related to our best practices what we what we tell our customers to do what so basically what I did is I created the several of JIRA groups so for example this I was not set up by tempo by default this is what I did and this is what I recommend you to do as well so for example I created here four specific rules which is the temple account administrators temple administrators temple resource managers and temple time track so and we will come into that a little bit later he also wear these two which permission schemes these roles groups are related to but so for example if you talk about the tempo tracking group this is very handy for example when you plan to roll out temple within a larger organization and you want for example only to start with with a small group to start with and then you can always add users into that so tempo can be hidden by default and this can be done I will go into that a little bit later on so so I will tell you then here why I did all those set up all those groups okay so just for you to know so it basically makes it easier for me to handle those here within one place so once I created these groups like I said this is a best practice guidance it's not a need to do so you can also of course handle that differently so but when again go I'm still back into JIRA so what you need to know is we have a setting here with in JIRA which is global permissions okay so once you have once you have temple installed you get a lot of temple or JIRA global permissions injected so these are the tempo timesheets except the temple count administrator tempo rate administrator template - traitors and temple team administrators okay so and what I'm going to do here for example and you basically will see that each year administrators get by default access to those what I want to do here is and this is why I created the JIRA groups beforehand I want for example to administer that differently so adjust for example to that from here I guess I give the team at ministry and I just want to delete the Giri administrators I don't want to have them access to to temple so this would be a different group here right and then we have the temple team administrators I get I do the same here I I select the group here for example I will also do that to the tempo administrators so you should be for example for be careful about the team administrator because there are also some kind of permissions behind that that are not really visible and maybe not all permissions are documented so so I would really remove these permission to only a handful people and then we have here the Temple account administrator and tempo rate administrator so I also want for example here I have certain groups available so this is what I did right so you of course can do that like you would like to do that but in very much what is the best practice is to to remove this functionality to only really handful of users and here's it comes when it comes to temple timesheet access okay so you will probably see here by default this is rolled out to everyone once you install that but you don't want to do that maybe so therefore for example I just created here group which is temple time tracking so for example here and I deleted JIRA administrators note it was the wrong group I think it's time citic says yeah damn here I want the JIRA software User's deleted by that and also the JIRA administrators so this makes me really I'm sure that only those people that I want to have access to temple only have exists to that so like I said by default it is rolled out to everyone and this is maybe not something that I would like to someone is complaining about time tracking that they have that within their system they don't want it or like I said for for if you want to roll it out you just make sure to roll it out only out tour a certain to a smaller group to start with so that's it for Sierra at the moment I will come to that too to the tear apart a little bit later but this is the first thing that you need to do check really those permissions here these those total permissions and the next thing that I'm going to do is going to little bit go into the configuration of temple ok so they are and if you go into manage apps here there are different configurations here on the left hand side but they are also considerations from the temple drop down menu here in the settings menu so they are two parts or two configuration areas for temple one area is only really for geo admins and this is not nothing that you can configure and this is here in the manage up section and the one thing that you just configured is the temple administrator settings and this is configured here in the in this or they have basically sets to this setting so there are you are basically able to configure this year but and all geo admins are have access here Tuesday to the left hand side so I don't want to go into each and single one because that is of course going to take a lot of time I just want to point out the world basic one and the web-based one is the global configuration so make sure before you before you go forward and roll out there might be some changes that you is that you can do here or how you can basically influence the lock time dialogue okay so so make sure that you set this or test this of course configure this and tested before so in very general this should be this should be setup fine and you can of course go go and and and get started with this what I always would recommend here is setting the maximum hours per day so this we usually prevents you from accidentally adding to too many hours for a day and also here so usually we can lock time 90 days in advance so so this is usually also what should be fine and there's one very important setting here which is the accounting setting and as you see it is by default unchecked so so these two settings here mean basically that you have an additional option to set build hours and I will I will check those on now so you can basically see that later on what influence that has when I track time or basically I can also do that right away so when I go here for example I will open up a new window with within tempo here so this is the the the tempo entrance of for the users and you will see for each single diet day you have these options to lock time and to plan time so planning time is always possible for for users so they can basically always plan the time for themselves that is not removable but and when we go into the lock time I will see here I have a very basic window here and have this billable option so I can basically distinguish here between available and worked hours and these hours where these hours can also then be pulled into the temple report so that could be where is a solution that many of our customers are using so that is therefore also something that I can for sure recommend especially when you are in a business like professional services or if you want to build your hours to someone else okay so very quickly from here so I don't want to go any further from here so these are the settings and I might come to that a little bit later here on when it comes to to schedule and access controls so these are two sections here that are really for advanced configuration and I will try to come back here later on if we have some time so and I just now want to get started with before I jump back a little bit later on to to the JIRA to the JIRA settings I just want to jump into the tempo settings here before and go through those settings that are available for tempo administrators like I said before tempo settings are still in the two areas one for the G Rodman's and one for the tempo admin and this section is only for tempo admins so and from here you go directly to the configuration we have a lot of we have a lot of options from here I don't want to go through them one by one I just want to go that in an order that should be where you should how you should get started okay so for example here the permission of view we cover that a little bit before so these are give you a little bit more explanation on those roads or on those global permissions that we just have set in JIRA so so I think we are covered here so but but the next step that we really need to do is to set up our users so of course our users are already set up but we need to create teams and therefore but before we create teams we also need to make sure that we have workload and holiday schemes configured and this is what I'm going to show you here first so first is what you're going to look into the workload schemes so and as I have a fresh temple installed you will probably see the same as me so temple is by default in tracking injecting a predefined workload scheme which is basically temple default Broflovski that's not very what I would like to see so so I would rather for example rename that here and say for example a 40-hour Brock loads game right so that's a little bit more descriptive of what it is basically doing what it is basically saying here I have eight hours for each for each day available but I also might for example do that a little bit differently so might for example say is thirty point seven point finds our workload scheme so it's very rarely done very quickly so I basically say here how much hours I'm going to work each day and let's say so I'm going to work on Friday only two and a half hours left so that's then five points five hours and thirty minutes and I can then add this for example or I could for example say 20 hours Brock lot scheme for example or whatever okay just would give you an impression of how you can do that or what you what you can do here so there are all kinds of things that you can do here so you can also see the members here and as you probably see here and this is for example what sample does by default it is signing all members to the default workload scheme here okay but we will see later on the way how we can change that and how you can move those members so you and this is for example I don't from to go here so once we've gone here it comes with the rock lot schemes I also go now next we go to the Holiday scheme so this is a default holiday scheme which is also injected by tempo and you will probably also so this is for example this is for example here always divided into two sections the fixed section on the empty and the floating sections of the fixed section is for example let's say Christmas vacation ok and to this one day and that's for example always on the same day of every year so I don't need to specify specific year for example and I can now here the floating ones good example for that is Easter vacation so I will stay here for example here the tape and so let's say for example here somewhere in April I think we have here Friday and at this one so I would probably them to do that for where I probably need to do that for Easter vacation 2020 for example ok and so I will then of course need to do that or specify that specifically for 2021 and so on so this is something that I need to that I need to populate here and the reasoning behind why I'm doing this is because this all these days that I'm going to specify here and the holidays games are getting reduced from my rock lock or from my rock duty within a temple or getting reduced from a cast capacity within temple planner for example okay so now once I have specified my rough let's games and holiday schemes the next thing that I'm going to do is I'm looking into the rolls so there are also some some rolls that I have and the reason is so they are different use cases why why and how you could use rolls so so for example that it might be very useful for example when you use tempo planner in order to to report or to spot for example available capacities per roll for example but we use that also within tempo timesheets to distinguish or to determine for example a price rate per roll so when we come later on to the count setup we will also see that I am able to setup price rates based on roles and this is the reason why I could why I buy a half rolls here and these rolls which is that you see here are a basic set of tempo but you might for example also setup your your rolls here or or create so I might for example here set in back-end developer and at this so but like I said this is only for relevance especially for tempo planner when you want to report on when you want to report on capacity but we are know now with with our newest version of tempo you can also use that these rules in order to report on these roles and tempo timesheets as well so they are also available as as a as a reporting option and grouping option for for timesheet reports and yeah so so this is a feature which has been released with a tempo 10.12 version which basically was released on marketplace today so this is a client version of tempo that you see here and so ok and we can also of course look into that how this looks like in the front that a little bit later if we have time to do so but now for example what is also brand-new feature for for for JIRA for tempo for server so this is only available for server is location so I am might for example enter my location here which is I am in Reykjavik Iceland right so I might also want to add that from here and I will okay so these are the three settings that I have roads locations replica dollar scheme and now I of course need to look into how I can assign those schemes to my users so and as you probably see you are tempo is going to assign all those default schemes locations and and yeah scheme some locations to to each member so you see there is no difference so I might for example now change that from here and look into ok I'm going to move different persons here to to to rock load scheme and say these persons they belong to thirty point seven point five rock Lots game for example okay and I'm going to move myself for example let's say two different location like Reykjavik can also set an effective date been here for several years so that might not be okay so so then for example you see here where each person user is located and what workload and hello scheme they are belonging to okay so this is so this is how we manage stuff but of course what we also need to do is is to create our teams right and this is the next step that we need to do so and they are of course always a lot of discussion is about and how you should set up your teams and so on so and and how many teams you should create and so on so there's of course no one one final final answer to that to that to that to that answer but what is very important you to know is is what what we use temple for tempo teams using for is a very very general or very much for example for for configurations or for permissions so and another one is reporting purposes so there are these two different ways that we are doing it and there might be another use case for example for tempo planner when you also have tempo planner and you want to filter by your teams or you want for example to assign to assign your tempo team to to an issue for example so you can basically you can filter on rather team then rather rather on the signees for example so that's that's also an option why you have why you have and should great teams within temple so and it will probably see from here you have the default temple team here and but the the temple team is very much empty as you see for example I will there there's the geo developers created or assigned to that but I could also say for example temple so I could for example now create a team with all my time tracking users so that's for example something that I can do here I have 40 members I select the team Li the team lead is always important because the team lead has the ability to to administer a team or to configure a team so therefore the team lead is important a program we have a lot of still a lot of information here that is not really necessary at the moment because that is more related to all the times of temple so for example program might is basically a selection of teams so if you want for example to to build a report on programs you can you can create of course that that program here okay and and then we have two other options here on the right-hand side we have we have the option to link that to project or we have the link it to boards so once again if you don't use tempo planner forget about these options here so these are only irrelevant for example specifically when you use temple planner so like I said when you use tempo planner you can use team in order to in order to assign an issue or multiple issues to team that's of course very helpful and what you now need to do or the the what is very important here are the permissions so like every state in the world beginning is that that many permissions are based on JIRA some of them are within temple and I will also come back to JIRA a little bit later in order to tell you how this is done within jira so within temple you can adjust these settings or these comfortably or these these permissions on on team level so and these are these settings are into view team baraq locks manage team brock locks or approve timesheets okay so we also have within temple the ability to approve the timesheet so or for users to submit the timesheet and there might also be a certain amount of users that are able to approve it or a user timesheet and therefore and therefore you they have this permission so and party for the team it always has all those permissions the member has no permission and we also see here these default injected here from temple so you can also for example forget about that okay so make sure that all those teams that have been set up by temple are really and that what you that what you need to do so for example we have this default temple team with all our time tracking users this might be of course not the use case with a new scenario but it might be for example a good idea and that you have for example that you create a permission roll here and so for example I would say here I could for example create role here which is resource managers and I picked a team for those and I want these resources to be able to view the team baraq locks okay so I can basically adjust all those permissions in one place that base it means I have one club team with all my users and give a specific role for a specific junior group and here for example I would at this these temporal resource managers to to this permission here so that basically means that all users within this loop have permission to view tear up locks so and here for example on top I could see say for example okay who has only specific users can can view that team so so by default it is to the resource managers and I could also for example say the JIRA administrators for example okay so making sure that this is my default team which is and I could probably rename that and say that just say for example temple permission team or whatever you okay so create it and save that and of course I can now of course also create a new team very quickly T so for example I create another lead for here so like a prob'ly said earlier make sure that you have that you have or restrict the success to to create those teams to only limited person persons that is really to be done that not that you not do not end up with all kind of teams within your instance okay and then you can of course add a member here for example per user and here again we have the add membership so when you want to when you want to add a member or when you want to add when you are adding a member to team you can also specify here for example the role that we have created earlier and also joining leave a date if you want to do so does only have the meaning or the joining and even date is important for example for tempo plan in order to see brand people are available to calculate the capacity and also for tempo times in order to to look into the permissions so for example after leaving date a user does not have any more than permission to view work locks from others for example so all that is check the commitment here is something that you should forget about we are going this is something which is going to be moved at some point later on so so we do not really support this anymore so therefore don't bother about that too much so just make sure that you at your members to your teams here okay so I'm very late so I really need to speed up in order to get things done that I wanted to do cover here so these are two two teams and before I so nothing that I need to mention here is of course the accounts so the count is always something that is very important for for a lot of for a lot of users for a lot of customers so that basically means an account gives you an ability to report across your projects okay so before we create an account we need for example creating a customer and the customer I can for example be something like internal one internal for example and let's just say one two three doesn't matter or I could also just say here for example I don't know what is the customer let's say I just say ABC ok so and this ABC this might for example is some external customer okay so once we have create some customers and I can create an account and I'm going to create here and so for example I would say here I would say for just for example for this a PC counter customer I say here professional services or I just say hours to be charged for example whatever I pick a category here okay I don't have any category I need to set it up I pick my ABC customer here and then I for example can also link that to a project episode that to you how that works I also need to have a lead okay do that okay here and this is my my account that I have done but I have seen now that I need to create my account categories and these are a little bit done somewhere else so I need to go back here to my to my to my tempo settings and from a tempo settings you might also see here in the account section that I have the account category so I say for example here I have a category name which is let's say professional services and this is of the type billable I just say here something fresh and I add this one and I also want to create another one this is for my other use case here which is basically vacation this is of the type of tunnel and it's just a vacay for example okay so and when I go back here to my to my temple instance of my accounts I just want to open that up it again and fun for example this is signed to a professional services okay so this is for example for each time that I'm going to charge a customer for example and I want to create another one which is for example vacation time so this is for example used for as you probably can imagine for internal use so this is my internal customer and depends on the kitchen so that also helps me and this is on what I'm going to link to internal project to okay so I have graded to two basic accounts one really for professional services former one for the case of vacation and now what I can do with this accounts and what I'm going to do now is a jump little bit back now to to JIRA to the JIRA administration settings so I go back here to JIRA and from JIRA you will also basically see that we have on the issue sections here we have different we see here for example the custom fields and this is also something that you need to that you need to be aware of that we have the tempo is injecting behind the scenes a couple of JIRA custom fields and this is for example here the account field and this is of the type tempo account custom field and but we also have the team field here as as as a as a field witches can be injected onto your screens so I could for example add this now to the account fields for my screen so I have already selected too many internal issues but I will also select it to my default screen and for the team for example I could also now add that to my default screen so and what that mean that very much basically means that now that I have created these that I have created these or edit these temple countries to my screens I will see here for example the the account field and what what you will see here so once I great for example an issue within my project web development project I will only have those accounts available that are that are linked to this project here okay so so this is the beauty of accounts and in a very similar way of what I'm going to do is when I select not this one here I have another internal project and I can also then okay I have not linked that yet so it's probably what I need to do I should be should be here linked to internal projects and I'm not sure if that so let's see probably I need to yeah so I need maybe to refresh that pace right so once for example I have so you see basically see here for this specific project I have only this account available ok so this is what you what you can or should do with your accounts and so basically that means for example that you can always create an a an issue for example for vacation 2020 but you still have a to to the vacation time issue so that so in that way you can for example keep track of your vacation for 2020 and always create new issues but always based on the same account and the account can also then be used in the temple reports to to report on ok so one last thing or one very important thing that I need to mention here and regards of JIRA that I already have shot you a little bit is the way of how to create or how to manage permission schemes so we have also seen that you can set permissions on on team level or in within tempo basically means that you can adjust for example who has the ability to to view rock locks from each other and who is able to to manage revellings or to a debt to to edit broke locks from user so all this can be done on tempo level but can also be done on JIRA level so and it is always very tricky to combine those permissions and to adjust that properly so it's working correctly or like you want it so what I want to point out here is from within the issues here I think it's here we have the permission schemes okay so and what I have done for example I have set up several permission schemes and I want to look into one of those for example the default software scheme which is a permission scheme that has been set up by by and that I've said that before and I can look into the permission schemes or into the permissions from here and from here you see of course the the basic set of permissions that you probably are aware of there are some permissions that I want to point out here for temple to be to be or that are as relying on one of those for example is the the Proust project permission so this is always important in order to be able to to view the or to look at the issues that you that you need to lock your track your time against and there's the added issue permission here the this one here so if you don't have at issue access you do have not the ability to add an access to edit the issue basically means you cannot lock work against an issue then we have the we have the time we have several time tracking permissions here and some of them are basic or native JIRA but some of them are also implemented by temple and one of those permissions is the view all rock locks permission here from here and another thing that tempo is doing is tempo is creating a behind the scenes a project role which is temple project managers okay so you and this is also some kind of best practice that I would keep here so you can also for example administer on on project level then who has or who has the ability to to view work logs from others okay so you can do that then by project role and then basically give or assign user to those project roles for each specific grr projects oh so this is something that you need to be aware of and also something that you need to bear where is the broken tissue permission so without the work on issue permission you can either lock time on a specific issue so then users get the rock tonight's message when they are logging their time okay so this is of course very click and you need to be you need to be aware of these several permissions and settings that we can do like I for example set here or what I did here is I created that additional or another permission scheme which is specifically for those internal issues so so all those permanent internal issues that I have just created against vacation time are against the specific project so I really want to keep that separated and keep and organize all my permissions in in a separate place and do that by creating an internal permission issue so when I look for example in to permissions from here you will probably see here that this is a little bit differently set up so for example I also give for example the the temple resource manager success - - to this view all work so so it's of course one way of doing it just what I want to say is make sure that you keep those internal issues or these very difficult issues or activities keep track of them somewhere else or in a different place in the different permission scheme so that could be that could be one good way on going forward ok yeah I spent far too many minutes on that all that stuff you go through so there are a lot of options of course available it might be confusing and of course it is confusing and of course you need to be aware of other things I just want to make sure that you have everything in place to get started that doesn't mean that you're all set and that you just can roll off everything so so really make sure that that you that you configure or your do test all your set up against the instance that where you want to implement temple so I also minutes or what I wanted to wanted to tell you hear something about is the gussets and I just want to show you very quickly how you can create a user dashboard for example like dashboard yes and so so when you have tempo installed make sure that you and when you look for tempo for example you see a lot of gadgets available some of them are might be very useful so I cannot go into each one of those but there's for example the the the temp overclock distributing data is a very good gas here to report on for example on epics we have the Tempe user time she progressed at for users for for each single users the tempo total Aras is four we can add this from here so there are a lot of options available but I would add for a user level for example the temple my works is also very important or might be very useful specifically when it comes to because from here you PO see what is planned for you today and and how much hours you need to track against how much hours you already have tracked so so there are a lot of options available from here and you just want to the way where you can find those caches and how you can add them to your dashboards so there's one question which is adding a group with in this permission granted to all the project within jira so yeah so so like I said there there are two two ways in order to configure the permissions in JIRA Hort or within tempo so one is really based on on project so you can basically see no matter where the person is coming from you can access you can give the permission to view all work locks on a project or you can also say for example or configure that that way it you just want to configure or limit the ability to view your clocks per team so you have these two options the team options or the team configurations down in Temple and the the permission or the permission on projects your project is done within jira permission scheme so and yes there's another there's another confusion here about assigning teams to specific projects so that might be of course very helpful for example when you so let's say I have temple take well for example so you might for example look into his sign is open when you want to when to and you want to look for example whereas the assignee in the team where reported in the team or in temple epic issue for example so there are a lot of take wealth functionality related both to teams but also to to other areas within temple as well so so yes so I there's one question regards of the regards to the commitment of of team member to team so like I said this is functionality that that was once used in within the team timeline which is still available of course but it's on its way to be so we are we are planning forward moving forward to to use the the resource overview more than the team timeline or instead so therefore we the commitment of team members is not anymore respected so therefore you should really plan for your user for example 80% of the time to work on specific projects and 20% for non related work for example yeah everything which is related to overhead so this is how that is being done now with in tempo planner instead of using the commitment hope that answers your question so let's see you have two other questions here so how to submit rock locks yeah okay so submitting work locks is of course one functionality which is built in within temple without being being configured specifically so so this submit for example button here is is always available and you can always submit your timesheet but of course you always need to do for example I have proof one that is approving your timesheet so I don't have one so I can't approve my time should now but that should be possible to configure within your team but when it comes to to submit timesheets so this is business for example also very a very specific topic so for example if you are interested here the temple time should prove this is really webinar where I go all into the details how how periods are configured how they are set up and and so so I can't of course cover everything today it's really starting point and should not be considered as more than this and but if you are interested in how temple time should will look into this tutorial here that might give you the answer that you're looking for