[jira] [Updated] (SUREFIRE-1417) In JIRA, what is the difference between issues and tasks? What's the best way to handle issues vs tasks?

["nicole wells (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUREFIRE-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nicole wells updated SUREFIRE-1417:
-----------------------------------
    Description: 
The configurable nature of JIRA means that you can define an Issue Type according to your business needs - it's a customisable, generic element with a handful of useful Attributes that can also be building with additional Custom Fields. You can then extend it further by creating customised workflows to associate to the IssueType, but it does help to have a basic handle on what JIRA does out of the box.

Issues are what JIRA started with, as a flexible Issues manager in its early days. Tasks are simply a variation of the IssueType. There is also some simple two level hierarchy within vanilla [JIRA Tutorial PDF]https://mindmajix.com/jira-training that can see a Task decomposed into a number of discrete Sub-Tasks - that hierarchy becomes useful when doing things like capturing time at the Subtask level that you want to see rolled up to the parent Task. 

I've built + deployed a range of customised JIRA instances where those initial base IssueTypes have been modified for a range of business scenarios to make it a useful Business Process Management platform, with the support of custom workflows and screens - there's a lot you can achieve with it, but I'd start by taking a deeper look at the following resources:
What is an Issue
Configuring Workflow

  was:
The configurable nature of JIRA means that you can define an Issue Type according to your business needs - it's a customisable, generic element with a handful of useful Attributes that can also be building with additional Custom Fields. You can then extend it further by creating customised workflows to associate to the IssueType, but it does help to have a basic handle on what JIRA does out of the box.

Issues are what JIRA started with, as a flexible Issues manager in its early days. Tasks are simply a variation of the IssueType. There is also some simple two level hierarchy within vanilla [https://mindmajix.com/jira-training JIRA Tutorial PDF] that can see a Task decomposed into a number of discrete Sub-Tasks - that hierarchy becomes useful when doing things like capturing time at the Subtask level that you want to see rolled up to the parent Task. 

I've built + deployed a range of customised JIRA instances where those initial base IssueTypes have been modified for a range of business scenarios to make it a useful Business Process Management platform, with the support of custom workflows and screens - there's a lot you can achieve with it, but I'd start by taking a deeper look at the following resources:
What is an Issue
Configuring Workflow


> In JIRA, what is the difference between issues and tasks? What's the best way to handle issues vs tasks?
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1417
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1417
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: documentation
>         Environment: windows
>            Reporter: nicole wells
>              Labels: windows
>
> The configurable nature of JIRA means that you can define an Issue Type according to your business needs - it's a customisable, generic element with a handful of useful Attributes that can also be building with additional Custom Fields. You can then extend it further by creating customised workflows to associate to the IssueType, but it does help to have a basic handle on what JIRA does out of the box.
> Issues are what JIRA started with, as a flexible Issues manager in its early days. Tasks are simply a variation of the IssueType. There is also some simple two level hierarchy within vanilla [JIRA Tutorial PDF]https://mindmajix.com/jira-training that can see a Task decomposed into a number of discrete Sub-Tasks - that hierarchy becomes useful when doing things like capturing time at the Subtask level that you want to see rolled up to the parent Task. 
> I've built + deployed a range of customised JIRA instances where those initial base IssueTypes have been modified for a range of business scenarios to make it a useful Business Process Management platform, with the support of custom workflows and screens - there's a lot you can achieve with it, but I'd start by taking a deeper look at the following resources:
> What is an Issue
> Configuring Workflow



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)