RANT: Atlassian Jira has nothing out of the box to filter basic admin search/filter

 As of 2025-09-05, there is nothing out-of-the-box with Jira to allow someone to find and identify an item with open sub-items or parent-items.

Scenario 1

There are several stories that were canceled that have sub-tasks that were not canceled. If you go to the default dashboard for yourself, all those sub-tasks still show up on your list. There is no way to find all the sub-tasks that have a parent-item that is Cancelled, Closed, or Done.

Scenario 2

I want to find stories that are not Cancelled, Closed, or Done that have all sub-tasks that are all Cancelled, Closed, or Done.

Work Life: Cannot get the value of a token type 'StartObject' as a string. (Jira and C#)

Using JSON deserializer for the response from Jira. This is caused by Jira admins updating one of the fields from a string to an object.

Is there a way to default problems to a value or null instead of failing? The field was a minor field but the entire report fails. Would like there to be a way to still get the report minus the one field.

C# provides the error on the character count. I had to use an editor to search the character count as my response is well over 10k characters.

Review: Jira Cloud (1 month usage after several years with Jira DC)

In summary, DC seems so much more intuitive. After a month, I am still struggling on how to easily navigate between pages. I like to think that I usually one of the faster adopters. Maybe I have reached the age where I no longer can adapt.

Most of my issues are with team-managed projects. For company-managed projects, I do not like that I have even less control than I had in DC. I used to be able to modify workflows. Seems dumb for me to create a ticket just to have our Jira admin rename a flow just because some useless developer cannot read or learn which forces me to create flows to say "(NOT FOR DEV USE)". [[Makes me really question the developer's ability to follow instructions or understand requirements]]

Epic Link

Now there is a concept of team-managed and company-managed. It seemed at first that the only difference is who manages the configuration. But there are lot of differences in the tool itself.

The biggest one is that the concept of Epic is completely different. And I don't even need to use Epic for my use. I just wanted to display the Epic Link in the details of the ticket. The field exists, but I cannot add it to the details. And of course, the web contains all the HOWTO on how to add it (for company-managed).

Board

I created two epics and several stories. After nearly throwing my laptop out the window, I associate the stories with the epics. Then you go to the default board. What would you expect to see?

Something? Yes, I was expecting to at least something but my board is completely empty.

Check my stories. They all have status To Do. Board has a column To Do but empty.

After some research and reading, you have to assign the stories before it shows.

One Board Only

So team-managed can only have one board. At least at the time of this. I found a page that Atlassian that it was coming in "next few weeks" but it was posted in May. It is now a few months.

https://jira.atlassian.com/browse/JSWCLOUD-17371?error=login_required&error_description=Login+required&state=a5593a0b-d488-4200-9323-c823f430a8c2

Team-Managed Project

This is very misleading. This is not a permissions issue. This is really a completely different solution (as can be seen that it used to be called NextGen). Looks like Jira is trying to assimilate it which does not make sense either. Why not just limit features from company-managed?

My recommendation is not to even try team-managed projects. It is not worth the headache of bypassing Company admins. For me this is kind of a pain because our group is essentially a subsidiary of a subsidiary of the main company. The love from corporate admins is quite robotic in that they are kind of effective but at the same time just feels like using a hammer to swat a fly.

Using Curl to test Jira API

curl -D- -X GET -H "Authorization: Basic [email + key]" -H "Content-Type: application/json" "https://[company].atlassian.net/rest/api/2/issue/[ticket id]"

[email + key] needs to be encrypted