Place: Newgen office.
Project Management features
Workflows are flexible and can be customized for each project and/or issue type, including subtasks. This allows you to track multiple, unrelated projects all within a single JIRA instance. For example, you can have ideas, tasks, bugs, purchase orders, anything that needs to go through a process – and each can have its own steps and transitions.
Workflow transitions can also have Conditions, Validators, and Post Functions.
- Conditions restrict the transition – for example, you would use a transition to set up an approval step, so that only users in a certain group (Managers, Approvers, Project Lead, etc) can transition the issue to the next step.
- Validators will check certain parameters – for example, a validator can be used to ensure that the comment entered by a user on the transition’s screen meets a certain criteria. If a validator ‘fails’, the Post Functions of the transition will not be executed and the issue will not progress to the destination step of the transition.
- Post functions are automatic actions that occur after a transition – you would use these to have a certain field updated, or have the issue assigned to a certain user or role. For example, when an issue has been ‘resolved’ you might have it’s priority automatically reduced to low.
Permissions are quite granular on the project level, and with JIRA Enterprise, they are also flexible by project roles and at the individual issue level.
- Issue operations, such as ‘edit’, ‘comment’, and ‘assign’ are all separate permissions which can be granted to a single user and/or a group. In JIRA Enterprise, you can also grant a permission to a project role. You can even grant a permission to ‘user is in custom field’ or ‘group is in custom field’. Role and custom field permissions allow you great flexibility to change things on the fly, without having to edit the permission scheme itself. Project Administrators have permission to edit project roles, so this gives them a small amount of flexible, project-specific user management.
- In JIRA Enterprise, you can add a layer of security at the issue level by using issue level security. This allows you to restrict users from seeing some issues within a project where they already have the ‘view’ and ‘browse’ permissions. This is especially useful if you’ll have external users on your system, or you need the ability to ‘restrict’ certain specific issues.
- The last area where permissions come into play is in the workflow. In JIRA Enterprise, you can restrict a workflow transition to users with certain permissions. There is a permission conditionthat you can add to any transition.
JIRA has a 4 level hierarchy: Project > Components (logical subsections) and Versions (phases/milestones) > Issues > Subtasks.