Jira Issue Workflow Configuration

-
Jira Workflow: A Jira workflow is a set of statuses, transitions & triggers that an issue moves through during its lifecycle, and typically represents a process within your organization. Workflows can be associated with particular projects and, optionally, specific issue types by using a workflow scheme.
Workflow can be defined for Story, Task, Bug, Sub-task & epic seperaltely or as a common based on subscription model opted by a user/organization.
It is also referred as "issue workflows" in Jira. Atlassian articel can referred here.

In order to configure a workflow user should first be aware of configured Jira process i.e. is it a company managed or team managed project setting in Jira while initial configuration was done. Note: Project once configured cannot be modified/migrated from team manager to company manager and vice-versa.

Below is the pictorial representation of how a user can identify if the project is company manager or team managed.

Detailed information on this is available here.

Pre-requisute:
  • User should be Jira Admin / Project Admin
  • User should be project member.
Steps on navigating to the Issue workflow in Jira (Team Managed)
  1. Select Project for which workflow needs to be modified.
  2. Navigate to Project Settings on left sidebar.
  3. Navigate and select Issue types from left sidebar.
  4. Select a issue type. e.g. Story.
  5. Select Edit Workflow on top right corner or .
    6. Note: A Standard workflow has ToDo, Inprogress & Done as a status pre-configured.

  6. Admin can add status, standard or custom from the top menu "Add Status" button and "Add transaction" i.e. an action to move the task to next state using button.
  7. Once the workflow and transactions are mapped and finalised user can apply same to project by clicking or .
    8. Note: Workflow status cannot be changed is already in user, in this case user will first need to create a new workflow and need to manually move the Issues to new status and de-activate the old workflow.

    User can also add triggers based on the subscription model to update assignee automatically while transitioning statuses.
    For Company Managed settings arcticle will be updated soon.

Comments

Post a Comment

Popular posts from this blog

How to verify systems designed in Business Analyst

-
Image
Verification is what most people think of when they hear the word testing — it’s the process of testing whether a business analysis solution does what it’s designed to do. During verification, the testing team (which may consist of developers, quality assurance [QA] people, and some business analysts [BAs]) put the software through its paces to both confirm that it operates as expected and ensure that it conforms to the design specifications laid out earlier in the project. Verification testing includes four phases — one pretest phase and three phases of actual testing. Smoke Test Also called a build verification test, a smoke test is a pretest that determines whether full testing can even begin in the first place. It reveals any simple failures in the solution that may prevent you from executing the tests in the next three phases. Some project teams may link this test to unit testing. Unit Test The unit test is the first actual phase of testing. It involves testing each uni...
Read more

Customizations: Oracle SaaS vs PaaS

-
Image
  It has always been a questions from customer, on what's the customization extent of SaaS and where one should approach PaaS services in Oracle universe. After working into this domain for 3+ years and having multiple iterations into multiple projects and tons of pre-sales in past few years this has brought me a good level of clarity to the extent where customers are happy to know the point when they should switch to PaaS. Understanding and practicing industry best practice should always be best practice for an organization as that helps to manage that for long run. As best systems are those which requires minimal of manual efforts to maintain. SaaS Customizations Page composer OTBI reports Custom Workflow - BPM Page Composer: For certain applications one can use Page Composer to configure application page components, such as page content and layout for other users.Here are the changes one can make using this tool: Add, move, delete, show, and hide fields ...
Read more

Agile Model

-
Image
Agile Method This article is a introduction to Agile software development methodologies and it's application. This is not only suitable for software developers but also for Team Leaders, Project Managers, Product Managers, Development Managers, Testers, QA Managers, QA Engineers, Technical Writers, UX Designers, anyone involved in the delivering software.It doesn't describe any code or technology it's an method or an software engineering model which helps to develop a tool to it's best requirements or goals. Agile Method is a combination of various sprint cycles initially of 1 to 4 weeks per sprint cycle. Deployment is alligned with the changing business need after the completion of every sprint cycle. Agile adapts of frequent feedback by delivering workable product after every iteration/sprint cycle end. In other words Agile Method is a series of short iteration/sprint cycles. Agile Model is an incremental version of multiple waterfall model cycle so,br the cha...
Read more