Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I set up pending issue types on Jira

Related to https://confluence.atlassian.com/jsbr/criar-pendencias-e-subtarefas-920354843.html

How do I set up this option (create pending) for the projects?

I'm Jira admin

1 answer

Hi @Dinamara Rodrigues , I would like to help but I don't speak Portuguese. Can you post english documentation, please?

@Martin Bayer _MoroSystems_ s_r_o__  thanks for your interest.

The artcle was written in portuguese. I've translated the page to english on browser. You can translate the page on browser, if you prefer. Above, the translation. Thanks

Create to-dos and subtasks
The basic components of any project are pending issues. Backlogs act as work packages that move through the projects' workflow, until the work is completed. A to-do can also have subtasks that can be individually assigned and tracked, as well as to-do-level security, to restrict the to-do to selected members of your team. On this page, you will find more information about creating and converting to-dos and subtasks, and how to set up security at the to-do level. If you want to know how to import multiple to-dos (and subtasks) using a CSV file, visit   to see the import process explained in more detail.

Before you start
You must have permission from the  Create Pending  project for the relevant pending project.

Create a to-do
Click  Create  at the top of the screen to open the Create To Do dialog box  . 
Select the   relevant project and  type of to-do  in the Create to-do dialog box  . 
Write a  Summary  for the pending and fill in the indicated fields, at least the mandatory ones marked with an asterisk.
If you want to access fields that do not appear in this dialog or hide existing fields:
Click the Configure Fields button   at the top right of the screen.
Click  Customize  and select the fields you want to show or hide by checking or clearing the relevant checkboxes respectively, or click  All  to show all fields.
When creating a to-do, the selected fields will be displayed.
Optional: to create a series of similar to-dos (with the same  Project  and to-do  type ), select the Create another check box   at the bottom of the dialog box. Depending on the configuration and the values ​​specified during the creation of previous to-dos, some of the fields in the new Create to-do dialog box may appear pre-populated. Make sure everything is fine before creating the next to-do.
When you are satisfied with the content of the pending item, click the Create button  .  


Cloning of to-do items
Cloning a to-do allows you to quickly create a copy of a to-do within the same project. The cloned to-do contains most of the same details stored in the original to-do, for example, Summary, Affects Versions, Components, etc. Some details are not cloned, for example, Job log, Comments, Pending history and links to Confluence pages. The pending status returns to the first step of the corresponding workflow, and resolutions are cleared. The cloned pendency can be linked to the original pendency, but this is not mandatory.

Open the pendency you want to clone.
Select  More  > Clone.  The Clone Pending screen   will appear.
You can edit the   Cloned Pending Summary if you wish.
If they are applicable to the pending being cloned, you can also select one or more of these options:
Clone subtasks , to copy existing subtasks
Clone attachments , to add existing attachments
Clone links , to add existing linked backlogs
Clone sprint values ,  to copy the complete and incomplete sprint values ​​from the pending
Click  Create .
Create subtasks
You can create subtasks in a to-do to break it up into smaller parts or to allow different aspects of the to-do to be assigned to different people. If you find that a subtask is preventing a pending issue from resolving, you can convert it to a pending task to allow them to work on it independently. And, if you think a to-do is simply a subtask of a larger to-do, you can also convert it to a sub-to-do.

You can only create subtasks if the administrator has enabled them and added the subtask to-do type to the project's to-do type scheme.

Navigate to the to-do that will be the parent to-do of the subtask to be created.
Select  More>  Create subtask . The Create Subtask screen   will appear.
Fill in the details as needed, then click  Create  at the bottom of the page.
Note that when creating a subtask, the following values ​​are inherited from the parent task:

project
security level of pending
sprint value, if any (only for pending JIRA Software) 
Tip : You can customize the Create Subtask screen   to show the most frequently used fields. To do this, click  Configure fields  at the top right of the dialog and use the All  and  Custom links   to switch between the standard screen and the custom settings. The changes are saved for future use.

Convert subtasks to to-dos
Navigate to the subtask you want to convert to pending.
Select  More>  Convert to  pending .
On the Step 1. Select the to-do type screen  , select a new to-do type (that is, a standard to-do type) and click  Next .
If the current status of the subtask is not a permitted status for the new to-do type, the  Step 2. Select the new status screen  is displayed. Select a new status and click  Next .
On the Step 3. Update Fields screen  , you will be asked to enter additional fields if necessary. Otherwise, the message "All fields will be updated automatically" will be displayed. Click  Next .
The Step 4. Confirmation screen   is displayed. If you are satisfied with the new pending details, click  Finish .
The pending will be displayed. You will notice that it is no longer a subtask, as a parent to-do number will no longer be displayed at the top of the screen.
Convert to-dos to subtasks
Navigate to the to-do you want to convert to a subtask.
Select  More>  Convert to subtask .
On the Step 1 screen,  select the parent to-do and the type of subtask , type or select the appropriate parent to-do type and the new to-do type (that is, a sub-to-do type). Click  Next .
If the current pending status is not an allowed status for the new pending type, the Step 2 screen  . Select the new status  is displayed. Select a new status and click  Next .
On the Step 3. Update Fields screen  , you will be asked to enter additional fields if necessary. Otherwise, the message "All fields will be updated automatically" will be displayed. Click  Next .
The Step 4. Confirmation screen   is displayed. If you are satisfied with the new pending details, click  Finish .
The pending will be displayed. You will notice that it is a subtask, as a parent to-do number will be displayed at the top of the screen.
Note : It is not possible to convert a to-do to a sub-task when the to-do has its own sub-tasks. First, you need to convert the to-do subtasks into individual to-do items. You can convert them into subtasks for other to-dos if you wish. Subtasks cannot be transferred directly from one to-do, you must first convert them to standard to-do items, then convert them into sub-tasks for the new parent to-do items.

Restrict access to a pending
When creating or editing a to-do, you can restrict access to your team members who are part of a chosen security level. In order for you to set the security level for a pending issue, the administrator must add it to the appropriate pending security level and grant you the "Set pending security" permission for the appropriate projects. 

Create or edit the relevant to-do.
In the Security level drop-down field  , select the desired security level for the pending. You will only be able to view the security levels to which you belong.
Save the pending. It can now be accessed only by members of the specified security level.
Users who are not members of this security level will not be able to access the pending or view it using any filter, query or statistics. 

@Martin Bayer _MoroSystems_ s_r_o__  thanks for your interest.

The artcle was written in portuguese. I've translated the page to english on browser. You can translate the page on browser, if you prefer. Above, the translation. Thanks

Create to-dos and subtasks
The basic components of any project are pending issues. Backlogs act as work packages that move through the projects' workflow, until the work is completed. A to-do can also have subtasks that can be individually assigned and tracked, as well as to-do-level security, to restrict the to-do to selected members of your team. On this page, you will find more information about creating and converting to-dos and subtasks, and how to set up security at the to-do level. If you want to know how to import multiple to-dos (and subtasks) using a CSV file, visit   to see the import process explained in more detail.

Before you start
You must have permission from the  Create Pending  project for the relevant pending project.

Create a to-do
Click  Create  at the top of the screen to open the Create To Do dialog box  . 
Select the   relevant project and  type of to-do  in the Create to-do dialog box  . 
Write a  Summary  for the pending and fill in the indicated fields, at least the mandatory ones marked with an asterisk.
If you want to access fields that do not appear in this dialog or hide existing fields:
Click the Configure Fields button   at the top right of the screen.
Click  Customize  and select the fields you want to show or hide by checking or clearing the relevant checkboxes respectively, or click  All  to show all fields.
When creating a to-do, the selected fields will be displayed.
Optional: to create a series of similar to-dos (with the same  Project  and to-do  type ), select the Create another check box   at the bottom of the dialog box. Depending on the configuration and the values ​​specified during the creation of previous to-dos, some of the fields in the new Create to-do dialog box may appear pre-populated. Make sure everything is fine before creating the next to-do.
When you are satisfied with the content of the pending item, click the Create button  .  


Cloning of to-do items
Cloning a to-do allows you to quickly create a copy of a to-do within the same project. The cloned to-do contains most of the same details stored in the original to-do, for example, Summary, Affects Versions, Components, etc. Some details are not cloned, for example, Job log, Comments, Pending history and links to Confluence pages. The pending status returns to the first step of the corresponding workflow, and resolutions are cleared. The cloned pendency can be linked to the original pendency, but this is not mandatory.

Open the pendency you want to clone.
Select  More  > Clone.  The Clone Pending screen   will appear.
You can edit the   Cloned Pending Summary if you wish.
If they are applicable to the pending being cloned, you can also select one or more of these options:
Clone subtasks , to copy existing subtasks
Clone attachments , to add existing attachments
Clone links , to add existing linked backlogs
Clone sprint values ,  to copy the complete and incomplete sprint values ​​from the pending
Click  Create .
Create subtasks

@Martin Bayer _MoroSystems_ s_r_o__  thanks for your interest.

The article was written in portuguese. I've translated the page to engligh on browser. 

Translation

Create to-dos and subtasks
The basic components of any project are pending issues. Backlogs act as work packages that move through the projects' workflow, until the work is completed. A to-do can also have subtasks that can be individually assigned and tracked, as well as to-do-level security, to restrict the to-do to selected members of your team. On this page, you will find more information about creating and converting to-dos and subtasks, and how to set up security at the to-do level. If you want to know how to import multiple to-dos (and subtasks) using a CSV file, visit this link to see the import process explained in more detail.
Before you start
You must have permission from the Create Pending project for the relevant pending project.

Create a to-do
Click Create at the top of the screen to open the Create To Do dialog box .
Select the relevant project and type of to-do in the Create to-do dialog box .
Write a Summary for the pending and fill in the indicated fields, at least the mandatory ones marked with an asterisk.
If you want to access fields that do not appear in this dialog or hide existing fields:
Click the Configure Fields button at the top right of the screen.
Click Customize and select the fields you want to show or hide by checking or clearing the relevant checkboxes respectively, or click All to show all fields.
When creating a to-do, the selected fields will be displayed.
Optional: to create a series of similar to-dos (with the same Project and to-do type ), select the Create another check box at the bottom of the dialog box. Depending on the configuration and the values ​​specified during the creation of previous to-dos, some of the fields in the new Create to-do dialog box may appear pre-populated. Make sure everything is fine before creating the next to-do.
When you are satisfied with the content of the pending item, click the Create button .

Cloning of to-do items
Cloning a to-do allows you to quickly create a copy of a to-do within the same project. The cloned to-do contains most of the same details stored in the original to-do, for example, Summary, Affects Versions, Components, etc. Some details are not cloned, for example, Job log, Comments, Pending history and links to Confluence pages. The pending status returns to the first step of the corresponding workflow, and resolutions are cleared. The cloned pendency can be linked to the original pendency, but this is not mandatory.

Open the pendency you want to clone.
Select More > Clone. The Clone Pending screen will appear.
You can edit the Cloned Pending Summary if you wish.
If they are applicable to the pending being cloned, you can also select one or more of these options:
Clone subtasks , to copy existing subtasks
Clone attachments , to add existing attachments
Clone links , to add existing linked backlogs
Clone sprint values , to copy the complete and incomplete sprint values ​​from the pending
Click Create .
Create subtasks
You can create subtasks in a to-do to break it up into smaller parts or to allow different aspects of the to-do to be assigned to different people. If you find that a subtask is preventing a pending issue from resolving, you can convert it to a pending task to allow them to work on it independently. And, if you think a to-do is simply a subtask of a larger to-do, you can also convert it to a sub-to-do.

You can only create subtasks if the administrator has enabled them and added the subtask to-do type to the project's to-do type scheme.

Navigate to the to-do that will be the parent to-do of the subtask to be created.
Select More> Create subtask . The Create Subtask screen will appear.
Fill in the details as needed, then click Create at the bottom of the page.
Note that when creating a subtask, the following values ​​are inherited from the parent task:

project
security level of pending
sprint value, if any (only for pending JIRA Software)
Tip : You can customize the Create Subtask screen to show the most frequently used fields. To do this, click Configure fields at the top right of the dialog and use the All and Custom links to switch between the standard screen and the custom settings. The changes are saved for future use.

Convert subtasks to to-dos
Navigate to the subtask you want to convert to pending.
Select More> Convert to pending .
On the Step 1. Select the to-do type screen , select a new to-do type (that is, a standard to-do type) and click Next .
If the current status of the subtask is not a permitted status for the new to-do type, the Step 2. Select the new status screen is displayed. Select a new status and click Next .
On the Step 3. Update Fields screen , you will be asked to enter additional fields if necessary. Otherwise, the message "All fields will be updated automatically" will be displayed. Click Next .
The Step 4. Confirmation screen is displayed. If you are satisfied with the new pending details, click Finish .
The pending will be displayed. You will notice that it is no longer a subtask, as a parent to-do number will no longer be displayed at the top of the screen.
Convert to-dos to subtasks
Navigate to the to-do you want to convert to a subtask.
Select More> Convert to subtask .
On the Step 1 screen, select the parent to-do and the type of subtask , type or select the appropriate parent to-do type and the new to-do type (that is, a sub-to-do type). Click Next .
If the current pending status is not an allowed status for the new pending type, the Step 2 screen . Select the new status is displayed. Select a new status and click Next .
On the Step 3. Update Fields screen , you will be asked to enter additional fields if necessary. Otherwise, the message "All fields will be updated automatically" will be displayed. Click Next .
The Step 4. Confirmation screen is displayed. If you are satisfied with the new pending details, click Finish .
The pending will be displayed. You will notice that it is a subtask, as a parent to-do number will be displayed at the top of the screen.
Note : It is not possible to convert a to-do to a sub-task when the to-do has its own sub-tasks. First, you need to convert the to-do subtasks into individual to-do items. You can convert them into subtasks for other to-dos if you wish. Subtasks cannot be transferred directly from one to-do, you must first convert them to standard to-do items, then convert them into sub-tasks for the new parent to-do items.

Restrict access to a pending
When creating or editing a to-do, you can restrict access to your team members who are part of a chosen security level. In order for you to set the security level for a pending issue, the administrator must add it to the appropriate pending security level and grant you the "Set pending security" permission for the appropriate projects.

Create or edit the relevant to-do.
In the Security level drop-down field , select the desired security level for the pending. You will only be able to view the security levels to which you belong.
Save the pending. It can now be accessed only by members of the specified security level.
Users who are not members of this security level will not be able to access the pending or view it using any filter, query or statistics.

Translation

Create a to-do
Click Create at the top of the screen to open the Create To Do dialog box .
Select the relevant project and type of to-do in the Create to-do dialog box .
Write a Summary for the pending and fill in the indicated fields, at least the mandatory ones marked with an asterisk.
If you want to access fields that do not appear in this dialog or hide existing fields:
Click the Configure Fields button at the top right of the screen.
Click Customize and select the fields you want to show or hide by checking or clearing the relevant checkboxes respectively, or click All to show all fields.
When creating a to-do, the selected fields will be displayed.
Optional: to create a series of similar to-dos (with the same Project and to-do type ), select the Create another check box at the bottom of the dialog box. Depending on the configuration and the values ​​specified during the creation of previous to-dos, some of the fields in the new Create to-do dialog box may appear pre-populated. Make sure everything is fine before creating the next to-do.
When you are satisfied with the content of the pending item, click the Create button .

According to the article, I should (as admin) be able to provide permission to Create To Do's for the projects. So, after that, the option (Create "Pending" or "To Do") would be available for the project.

I don't know what the "Pending" or "To Do" means. If it's an Issue Type (I couldn't find that), or anything else. 

hi @Dinamara Rodrigues , yeah, I do not know what "Pending" means in this context too. There is no such keyword in Jira (or I didn't see it in previous 6 years :)).

Pending is maybe a Backlog of issues of any type. DO you know what backlog in Jira is? Or do you need something else? I'm really confused , to be honest :)

Like Dinamara Rodrigues likes this

@Martin Bayer _MoroSystems_ s_r_o__,

I'm very sorry. Let me try to explain.

Someone on my team asked me about this "Pending" issue. According to him, in his last job they used to have this "pending" option creation and sent me this article to implement it.

I tried to follow the steps outlined in the article. But I couldn't figure out how.

So, I asked for help to try to understand what this feature is and how to implement it.

But I'm really giving up. I will try to write feedback in the article.

I really appreciate your attention. If I have any news about this, I will let you know.

Thanks

Ok @Dinamara Rodrigues , it might be some outdated docs or who knows. It will be cool if you will share the news with me :). Thank you :)

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you