youngmon/atlassian-qna huggingface dataset:
Display Sub-Tasks on Scrum Board
Asked by David Smith:

If been using Jira for like 15 years happily seeing Sub-Tasks as cards on the board.

Just started a new project, on a fresh atlassian Cloud install (basic version), and sub-tasks don't show except for "Group by Sub-Task" which is not a usable view. Just a little "hierarchy" icon telling you there are sub-tasks.

**Is this true - atlassian have decided sub-tasks should not be on the board?**

Or a i missing a new config somewhere. (new install, this is the only project, I am admin, sub-tasks are in the Issue type Scheme \[a change I made\], no board filter etc etc I have checked these things)

(\* been on a data centre older version for last year or so)

thanks

Dave!


Answers:
author: David Smith
body: going to answer my own question as I have found the answer!

your first project defaults to team-managed project, which for some reason has removed this long standing functionality. Moving to company-managed project you can get back to having sub-tasks on your board.

see [Dave Mathijs](https://community.atlassian.com/t5/user/viewprofilepage/user-id/2662590) comments in this answer <https://community.atlassian.com/t5/Jira-questions/Showing-sub-tasks-on-JIRA-board/qaq-p/2202230>


author: Manoj Gangwar
body: Hi [@David Smith](/t5/user/viewprofilepage/user-id/507105) ,

Welcome to the Atlassian Community!

Sub-tasks are of little use in a backlog, they're not rank-able outside their parent issue, and are not sprint items themselves, so there's not a lot of point in seeing them.

You can get a view of them in a backlog by adding the "sub tasks" field to the backlog view of an issue, but of course, that's just going to tell you "this sprint item has some sub-tasks", there's nothing you can do with them in the backlog.

comments: author: David Smith
body: Thanks for your thoughts.

sub-tasks are just another level in the backlog hierarchy. Often a workaround for many many years before atlassian had more levels / sorted out using Parent. They ARE part of the tasks to deliver the sprint, and the functionality we have had for many years of seeing the subtasks nicely grouped under a story/task on the board is one of the most used features across jira's user base in my experiance and across my global organisation.

E.g. say a certain User Story has a one off specific need for a document to be created before it is "Done", doing a sub-task tracks that showing it nicely in the board view. Yes you could do a linked Task but then you are losing the visual and have to go searching for the related item. The board is meant to be visual it stems from doing it physcially which is how we would do it if we want back to using post-it notes!

I think it is a massive backwards step if atlassian are tyring to remove them from the board.


Tags: board

cloud

jira-cloud

sub-task
New "This component may be incompatible" error on automation
Asked by Rees_ Ian:

Recently a few of my automations that have always worked before, now produce a "This component may be incompatible" error when the rule is updated. However, the rule still runs successfully so I can ignore the error. I have simplified the rule down to as shown i.e. trigger when a version is created then create an issue in the triggering project. Why has this suddenly started producing an error when it was ok before![automation error.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/346569iE97171012AB195BE/image-size/large?v=v2&px=999 "automation error.PNG")


Answers:
author: Trudy Claspill
body: Hello [@Rees_ Ian](/t5/user/viewprofilepage/user-id/4878063)

Referencing [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) 's response on this post:

<https://community.atlassian.com/t5/Jira-questions/Automation-error-This-component-may-be-incompatible/qaq-p/2746714>

...the introduction of that warning message is described here:

<https://community.atlassian.com/t5/Automation-articles/New-Improvements-for-Jira-and-Confluence-Automation/ba-p/2744140>

He also noted that he has encountered false-positive occurrences of that warning.

I created a rule using the same two components as you and did not get the warning, so you may be encountering a false positive occurrence.


author: Trev Angle
body: Hi [@Rees_ Ian](/t5/user/viewprofilepage/user-id/4878063), this is Trevor from the Confluence automation team. I saw your post and flagged it with the automation team in charge of Jira components, and they confirmed that this is a bug. I believe they've released the fix now, so hopefully you should stop seeing this incorrect validation warning!


Tags: automation

cloud

cloud-automation

jira-cloud
different teams - same workflow - different status definitions - how to effectively report as a PM?
Asked by Julia Maes:

I have 2 teams working on Jira using the same scrum workflow, but some statuses have different meanings between teams.

For example, after an issue is created, the first status is To Analyse, then it moves to 'To Amigo' and then to 'To Poker'. 'To Amigo' means brainstorming about technical viability and 'To Poker' means allocating time to the issue. team A does this in 2 steps, but team B does this in one step.

The whole workflow consists of these differences in status definitions, which makes it very difficult for the Project Manager to have a global view and make global reports.

As no team is willing to adapt to the status definitions of the other team, is there another way around to make reporting and dashboard view more easy?

Is writing JQL Queries and combining them for a unified view, in combination with dashboard building an option?

(I'm a beginner at Jira, help needed!)


Answers:
author: Dan -minware-
body: Hey [@Julia Maes](/t5/user/viewprofilepage/user-id/5588834) -

Full disclosure, I work for a 3rd party marketplace partner called minware. We make it super easy to define the "Definition of Done" for each of your teams and can handle this request.

Here is an example screenshot:

![minQL-definitionofdone.png](https://community.atlassian.com/t5/image/serverpage/image-id/346661i4C4652852F25BC54/image-size/large?v=v2&px=999 "minQL-definitionofdone.png")

All we need to do is modify the "filter(subType.in('green'))" and set that to the status or custom field you want to use.

We offer a free trial if you want to check it out!

comments: author: Dan -minware-
body: [@Julia Maes](/t5/user/viewprofilepage/user-id/5588834) -?are you still looking for a solution?


author: Jim Knepley - ReleaseTEAM
body: Does it need to be the same workflow? You can create a new workflow for team B that doesn't have the "Amigo" status or related transitions.


Tags: cloud

jira-cloud

jql

status
How do you import linked issues from a CSV?
Asked by Garrett Boller:

I've read through and attempted to replicate the guide

<https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-in-jira-740262715.html>

and I'm still unable to replicate with results. I don't have the option of 'Blocks' or 'Clones' on my field mapping in the import. What field should I be mapping with the linked Issue ID to?

TIA!


Answers:
author: Sanam Malleswari
body: Hi [@Garrett Boller](/t5/user/viewprofilepage/user-id/5588831) ,  

Please follow below path to add 'Blocks' or 'Clones' into Jira and added issue link types will appear on field mapping in the import  

gear icon--\> Issues--\> Issue features--\> Issue linking  

Please observe below snap.   

![Screenshot_10-9-2024_193326_jira.tpicapcloud.com.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/346576i1B88076F8ACE16F4/image-size/large?v=v2&px=999 "Screenshot_10-9-2024_193326_jira.tpicapcloud.com.jpeg")  

comments: author: Garrett Boller
body: TYSM!


Tags: cloud

jira-cloud

jira-software
"Type" dropdown has vanished from the "backlog" feature for a specific board
Asked by Roy Koren:

Hi,

In the "backlog" feature, there's the "Type" dropdown that usually exists on different boards.

For an unknown reason, it is completely missing for a specific board we use regularly.

I have no idea where did it go and why it appears on some boards while on this board it doesn't.


Answers:
author: Trudy Claspill
body: Hello [@Roy Koren](/t5/user/viewprofilepage/user-id/5167763)

The "Type" dropdown is for filtering the issues based on Issue Type.

It will show only the Issue Types for issues that are included in the board. The list will not include either Epic or Subtask issue types.

The option will appear only if there is otherwise more than one Issue Type included in your board.

Do you have more than one Issue Type included in your board?

comments: author: Roy Koren
body: Thanks Trudy for the (very) quick response.

Not sure if perhaps I wasn't clear enough, but it **did** work before on the specific board and one day suddenly disappeared, **only on this board**, while it was working on other boards (all have multiple issues since it's the same project) at the same time.

Anyhow, the morning after (yesterday) it changed back and now it's working as normal..

Not sure if it was a bug or I don't know what but now it's working, so we're all good.

Thanks again.


Tags: cloud

jira-cloud
Foce list view field layout
Asked by BSU:

Hello Guys,

I wanted to force the list view layout that I created, to the whole organization, like below.

I don't mean filters, those are already set up, but there is an issue where my layout isn't being applied to the whole Org, is there any way to to it?

![obraz_2024-09-10_151153052.png](/t5/image/serverpage/image-id/346560i96EC03751B02E988/image-size/large?v=v2&px=999 "obraz_2024-09-10_151153052.png")


Answers:
author: Hannes Obweger - JXL for Jira
body: Hi [@BSU](/t5/user/viewprofilepage/user-id/5587573)

welcome to the community!

The list view is currently "per user". You may want to watch (and perhaps upvote) this feature request: [JWMCLOUD-98](https://jira.atlassian.com/browse/JWMCLOUD-98).

As [@Sanam Malleswari](/t5/user/viewprofilepage/user-id/5506444) pointed out (thank you!), my team and I work on a Marketplace app in which your use case would be easy to solve: [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2808113). It also comes with a long list of advanced features - including support for (configurable) *issue hierarchies* , *issue grouping* by any issue field(s), *sum-ups* , or *conditional formatting* - and works across any number of projects.

This is how it looks in action:

![jxl-basics.gif](https://community.atlassian.com/t5/image/serverpage/image-id/346792iFCE017AF780982B6/image-size/large?v=v2&px=999 "jxl-basics.gif")

Any questions just let me know,

Best,

Hannes


author: Sanam Malleswari
body: Hi [@BSU](/t5/user/viewprofilepage/user-id/5587573)  

You can achieve a list view field layout using the JXL add-on.  

Please refer to the following link for more details.  

[https://community.atlassian.com/t5/Jira-Work-Management-Questions/How-to-make-a-List-view-that-is-the-same-for-all-users-in-a/qaq-p/2397405#:\~:text=and%20just%20to,share%20with%20others](https://community.atlassian.com/t5/Jira-Work-Management-Questions/How-to-make-a-List-view-that-is-the-same-for-all-users-in-a/qaq-p/2397405#:~:text=and%20just%20to,share%20with%20others).

JXL Add-on link: [https://marketplace.atlassian.com/apps/1224710?hosting=cloud\&tab=overview\&utm_source=atlassian-community\&utm_medium=referral\&utm_content=2397405](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2397405)


Tags: cloud

jira-cloud
Issue with automation doing remaining estimate = original estimate - time spent
Asked by rob_jeal:

I have some automation which seemed to work for a while doing the below. The issue that seems to be happening now is that the automation keeps cycling as it's seeing the remaining estimate field updating and then running again.

**WHEN**

value changes for time tracking for edit issue

**IF**

{{timetracking.timespent}} does not equal Empty

**THEN**

edit remaining estimate -

{{#=}} ({{fieldChange.to}} - {{triggerIssue.fields.timetracking.timeSpentSeconds\|0}})/60{{/}}m

**Example of the cycling issue we're now seeing**

![Screenshot 2024-09-10 141453.png](https://community.atlassian.com/t5/image/serverpage/image-id/346564iA95F9235BCF89854/image-size/large?v=v2&px=999 "Screenshot 2024-09-10 141453.png")


Answers:
author: Trudy Claspill
body: Hello [@rob_jeal](/t5/user/viewprofilepage/user-id/5294834)

The Log Work feature will automatically reduce the Remaining Estimate when time is logged if there is a Remaining Estimate value on the issue where the time is being logged.

What is the reason behind forcing that through an Automation Rule?

comments: author: rob_jeal
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) It was to capture changes to original estimate sorry. So if the original estimate is increased/decreased, the automation deducts time spent from the new original estimate, to provide the new remaining estimate.


author: Trudy Claspill
body: On the Rule Details page is this box checked, and if so was that a recent change?

![Screenshot 2024-09-11 at 1.06.51?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/346760i468F1E8E68AF4782/image-size/large?v=v2&px=999 "Screenshot 2024-09-11 at 1.06.51?AM.png")

That could cause the rule to be re-triggered because the rule itself is changing the time tracking data.


author: rob_jeal
body: Thanks [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) that is ticked but not a recent change but maybe the issue has been going on longer than I thought! I'll test it with that unchecked.. Thanks


author: rob_jeal
body: that seems to have worked, thank you!"


author: Bill Sheboy
body: Hi [@rob_jeal](/t5/user/viewprofilepage/user-id/5294834)

Adding to Trudy's suggestions and your findings...

If that option to allow rule trigger was enabled for a while, perhaps it was selected incorrectly by a rule-writing person. And thus **their rules may be consuming your monthly, automation usage limit:** <https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits>

Please consider working with your Jira Site Admin to check usage and inventory all rules to determine if other rules have the setting enabled. By default that option is disabled, and should only be used when you want the actions of one rule to trigger another.

Kind regards,  
Bill


Tags: cloud

jira-cloud
Unhide Hidden Fields when updating issues
Asked by Jodie Parsons:

Hidden Fields

![Hidden Fields.jpg](/t5/image/serverpage/image-id/346544iBBC601436DAD6AC3/image-size/large?v=v2&px=999 "Hidden Fields.jpg")

In a project, I've created two new drop down fields. When I attempt to add the new fields to a different project I can't see or search for the new fields because I'm presented with a 'Hidden fields'. (See above)

I didn't originally create the project but I am the Jira Administrator and owner of the project.

Any ideas how to unhide this so I can select the fields I want to add to an issue type.

I'm conscious of messing anything up in the settings so does anyone have any straight forward suggestions.

Thanks

Jodie


Answers:
author: Nikola Perisic
body: Hello [@Jodie Parsons](/t5/user/viewprofilepage/user-id/5131687)

Have you added those two fields to the screen of that project? It needs to be added to the screen first. Second, when you are creating an issue make sure that from Show fields option you check both of those fields (unless you want these fields to be only on the edit/view screens).

comments: author: Jodie Parsons
body: Hey Nikola.... no I've not added the two fields to the screen of that project.....how do I do that please?


author: Nikola Perisic
body: Navigate to your settings (cog), then choose Issues \> Screens \> Find your project based on the project key \> Search for your custom field and add it in there


author: Jodie Parsons
body: Thanks for trying to help Nikola

I've followed your steps but when I click on 'screens' I see this...

The project was not originally created by me. The person who created this no longer works for the business but I am the Jira Administrator and owner of this project. Also I noticed it's a company managed project. Not sure if any of these factors might be hindering me....

When you say 'Find your project based on the project key' I expect to see that option when clicking on 'screens' but this is all I see in the screenshot...

![Screens.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346545i9BAF89DF0109AB5C/image-size/large?v=v2&px=999 "Screens.jpg")


author: Nikola Perisic
body: What I've meant was, on the right top corner of your screen you will see a cog icon. When you click on it, you would need to find the option Issues, you should have this, since you are the Jira administrator. Then you will find the option Screens.![Screenshot 2024-09-10 at 14.23.02.png](https://community.atlassian.com/t5/image/serverpage/image-id/346546i54513D9D83250DA2/image-dimensions/399x509?v=v2 "Screenshot 2024-09-10 at 14.23.02.png")


Tags: cloud

hidden-fields

jira-cloud
Jira Checklist Limits
Asked by anne_gerten:

Hi,

with the upcoming Checklist Item limits (limit of 10,000 checklist items per Jira instance for Checklist for Jira \| Free), I need some help identifying and modifying tickets:

* How can I create a Jira Filter to show number of tickets with checklists in a project?
* How can we mass remove checklists from tickets (\>100k tickets)

Thanks,

Anne


Answers:
author: Oleksandr Melnyk
body: Hey.

To remove the checklist from tickets - disable the Checklist in the target project


author: Daumantas Butkus
body: (Not an answer)

Hey, from what I gathered this change is due to large teams using this free app with excess of 10k checklist items.

<br />

What sucks is it counts checklists items regardless of the status of the task (Resolved/Unresolved)

What I think I'll do and it seems to work is, filter out all of the tickets that contain checklists with a simple

"Checklist Text (view-only)" IS NOT EMPTY

and the do a bulk change to old tasks modifying only the "Checklist Text" field.

It does clear out the checklist, but it will only be apparent after a day as the total item count updates daily.

For later tickets I feel like the best course of action would be to automate tickets so that if they haven't been updated for more than x amount of time it clears the ''Checklist Text'' field.

Will update if I find something else.


Tags: cloud

jira-cloud
Is it possible to customize the Multi-line text filed as tabular format?
Asked by Perumal M:

Is it possible to customize the multi-line text field to a tabular format?

I have one custom filed name called General this type is a Multi-line text field. I want to make this filed as format below.

![Screenshot 2024-09-10 162800.png](/t5/image/serverpage/image-id/346523i35B466267BAA0932/image-size/large?v=v2&px=999 "Screenshot 2024-09-10 162800.png")

The table should come here.

![Screenshot 2024-09-10 163005.png](https://community.atlassian.com/t5/image/serverpage/image-id/346525iAFAD2F12538AB64C/image-size/large?v=v2&px=999 "Screenshot 2024-09-10 163005.png")


Answers:
author: Marc - Devoteam
body: Hi [@Perumal M](/t5/user/viewprofilepage/user-id/5305127)

This should be feasible.

The render of the field should be Wiki Style render, to be set in field configuration.

Then in the default field value, use the markup language.

See; <https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=tables>

comments: author: Perumal M
body: Hi [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) ,

I want this feature to be available throughout the entire ticket life cycle, including creating, editing, and viewing.

Could you please explain the way to do it? Your help would be appreciated.

Thanks.


author: Marc - Devoteam
body: Hi

<https://confluence.atlassian.com/adminjiraserver/configuring-renderers-938847270.html>

<https://support.atlassian.com/jira-cloud-administration/docs/configure-a-custom-field/>

example:

<https://community.atlassian.com/t5/Jira-questions/Having-trouble-with-rendering-default-values-in-a-custom-text/qaq-p/1769929>


author: Perumal M
body: Dear Marc,

Thanks for sharing the details with me, will check the same.


Tags: data-center

jira-data-center

jira-server
How to map subtasks to parents using the new Jira Importing Tool
Asked by Alissa Stark:

Hi, when using the old Jira importing tool, you were able to import subtasks by mapping their parent IDs to the issue IDs of the parents. How can you import subtasks using the new Jira importing tool when there is no 'Parent ID' option available to map from a CSV file?


Answers:
author: Nikola Perisic
body: Welcome [@Alissa Stark](/t5/user/viewprofilepage/user-id/3753439)

You can still use the Parent instead of Parent ID where within the Parent column you will enter the actual IDs'.

Reference:<https://confluence.atlassian.com/jirakb/csv-import-parent-child-mapping-1096095688.html>


author: Jack Brickey
body: Hi [@Alissa Stark](/t5/user/viewprofilepage/user-id/3753439) , I have not tried an import recently but can you not map the issue key as the parent?


Tags: cloud

importing

jira-cloud

jira-software
Problem when opening a project it gives 500 error
Asked by Kateryna:

![image.png](/t5/image/serverpage/image-id/346516iD2C554E478E867B5/image-size/large?v=v2&px=999 "image.png")


Answers:
author: Nikola Perisic
body: Hello [@Kateryna](/t5/user/viewprofilepage/user-id/5554833)

Start in the incognito mode and try again. If this doesn't work , something is wrong from the Atlassian backend. You can raise a support ticket for them here: <https://support.atlassian.com/contact/>


author: Manoj Gangwar
body: Hi [@Kateryna](/t5/user/viewprofilepage/user-id/5554833) ,

It seems like an issue with the Atlassian end.


Tags: cloud

jira-cloud