Before reading this chapter, it is recommended to get in touch with the general information about planning with CapMan. There you will learn about all the terms that will meet you at user interfaces presented in this chapter.
This section documents how you can plan with CapMan your Jira projects and versions. You will see that the CapMan plans can be associated with Jira and thus you receive the actual data for your plan data by means of Jira TimeTracking.
If you are using CapMan for Jira plugin, then you get in Jira’s project and version overview a new tab called CapMan, which allows you to organize your plans with the association to Jira:
If there was no plan for a Jira project or version created, then you will get the following user interface where you can create a new plan:
After drawing up the plan over the user interface above, the CapMan project will be automatically associated with the Jira project / version. It displays the following interface for a newly created plan:
Now you can assign your employees to the project over the CapMan plan view. The project assignment dialog displays you additional information about the utilization of employees:
If your employees have not booked any working time in Jira, then your finished plan might look like this:
If your employees record their working time on Jira issues of projects which are planned with CapMan, then you can see your plan data with the actual data in the CapMan plan view:
If your planning is linked to a Jira version, then your employees need to specify this version in their issues as the Fix Version so that CapMan can match time records for the version which you are planning.
With the appropriate configurations you can define the users who can work with the CapMan tab in Jira. Thanks to the support of Jira project roles you can assign permissions even at individual projects. The following permissions can be assigned:
|No permission||The CapMan tab is not visible to the user.|
|Read permission||The CapMan tab is presented to the user in a read-only view, if the plan data for the current jira project has been already created. If the jira project is not associated with a CapMan project, the CapMan Tab will be not visible to the user.|
|Full permission||The user will be able to create and modify CapMan projects.|
|Plan proposer permission||The user can only create and modify CapMan projects with the proposed plan state. The plan state can be changed to final or preliminary only by a planner with the full permission. For existing projects, which have a different status as a proposed plan, the user receives a read-only access.|
On the one hand the permissions must be configured over CapMan roles and on the other hand about the Jira Project Roles. The following roles must be set in CapMan to access the CapMan Tab.
|PLAN_READER||The user gets the permission to read the CapMan plans for Jira projects and versions.|
|PROJECT_PLANER||The user gets the full permission to access the CapMan plans for Jira projects and versions.|
|PROJECT_PLAN_PROPOSER||The user gets the plan proposer permission to access the CapMan plans for Jira projects and versions.|
In order to apply the permissions above for the Jira user interface, the Jira user must have the corresponding Jira project roles. In CapMan application.properties configuration file exist for this purpose four properties that are used in CapMan to determine which jira project role with what kind of permission is authorized:
|application.capman.gadget.permission.view.projectlead||true||The project leader receives the read permission for the plans of his Jira projects. Can be true or false.|
|application.capman.gadget.permission.view.projectroles||Developers||Comma-separated list of project roles which grant its assigned users the read permission for the projects.|
|application.capman.gadget.permission.edit.projectlead||true||The project leader receives the write permission for the plans of his Jira projects. Can be true or false. To modify the plans, the project leader needs also the read permission, to see the existing plan in the corresponding user interface.|
|application.capman.gadget.permission.edit.projectroles||Developers||Comma-separated list of project roles which grant its assigned users the write permission for the projects. To modify the plans, project roles also need to have the read permission, in order to see the plans in the corresponding user interface.|
To authorize a user with the required permission for the use of the CapMan tab in Jira, both the Jira project roles and the listed CapMan roles must be associated with the user.