Nic Brough -Adaptavist- Expert

OK. Not a lot more we can tell you when you have not given us anything to look at.

We are a community of people with an interest in Atlassian, we are not your administrators, and we can't know who they are. You are going to need to look at what you can in the space to try to identify the space owners. See if you can see anything in the space settings, or the top level pages that identify the owners of…

It's a long story behind it, but the answer here is "do not export the 'time in status' field". It is not really a field, and it's certainly not one intended for humans to read. The data in it is encoded in a way that * Makes it look like nonsense to humans * Is readable by the code in Jira that knows how to show it to…

No, the display of the field is not configurable like that. The code only has one response to Jira when it says "what do I show to the user?" to the field.

Yes, you can use the linkable headings - see https://support.atlassian.com/confluence-cloud/docs/insert-the-anchor-macro/ (to explain the odd name of this url, there used to be an "anchor" macro in Confluence, but the functionality was absorbed into the linking stuff)

Not on Cloud, the ability to change the pattern was removed to prevent people using ones that break things

Look at the field at the root of this as just one example - status * Q: Where are we with this item? * A: The status tells us that * Q: Ok, great, what's the status? * A: Which one of the 45 status available do you mean? * Response: I have no idea,* why the hell have we got 44 totally useless status that don't tell me…

I'm sorry, that simply sounds like your screen is the wrong size, and the browser is being forced into trying to re-arrange things in a way that doesn't really work for you. Could you give us a screenshot?

What do you mean "they don't display correctly"? What is wrong with them?

I'm not sure how many different ways this can be stated. In any organisation, "fielditis" is a symptom of a broken set of processes, and is likely to be wasting a lot of resources. Anyone suffering it should be telling the upper layers that there is a problem that can't be fixed by sticking your head in the sand, botching…

It's not there, you can't change it on Cloud.

Actually, I wouldn't call it a customer support failure, it's actually encouraging the customer to improve their process and usage...

You could duplicate it, but you'll make yourself the problem that you'll need to capture "move issue" and "project changes category" and rebuild the data on those events. I'm not sure it is of much use to the end user directly either. Whilst there is no apparent field for it, most people don't much care about the category…

I think you have clicked on "help with a system we use for docs/support", rather than "help with Breeze" We are an Atlassian forum, not a Breeze one, and I found something called Breeze that is hosting some docs on Atlassian's Confluence. I'm afraid it is unlikely anyone here can help you with Breeze directly.

Jira does not display (most types of) fields that are empty. If you edit the issues, you'll find you are offered the new field, assuming you've added it to the edit screen for that project.

Have you tried clicking the menu?

Confluence does not handle content in HTML. You should be using macros or apps that can provide drop-downs, not simple html in the body.

Yep, but it's not a bug, because it's working as intended! Atlassian have closed the requests for a change with "won't do" type messages, indicating the "workaround" is essentially "do something about your fielditis". Not ideal.

A cascading select list only has one value, you can't give it multiple ones. The database structure doesn't support it, let alone the back-end code or UI. There's nothing you can do with Behaviours or even Scriptrunner directly, you'd need to write an app that provides a new custom field type. What you could try with…

If you have Scriptrunner, then combining bits of these two scripts should do the job: https://library.adaptavist.com/entity/identify-the-groups-of-a-user will get a list of groups for the currently logged in user. https://library.adaptavist.com/entity/update-the-value-of-custom-fields-through-the-script-console shows you…

@Randy Wilson- there's nothing they see as a "fix" - this was a deliberate improvement made a few years ago. You would be better saying "a design flaw that affects people already suffering fielditis"

There is no "sub-project" functionality in Jira. But your actual request is quite simple - you just add a select list field for "functional area". Where are you stuck on adding a new custom field? Do you have the permission to do it (Jira admin for classic projects, or project admin if it is a next-gen project)? If you do…

You do know I'm quite familiar with Jira? Only been using it since version 2... I've spent most of my career with Atlassian stuff seeing problems like this, and "it's not going to happen" is something that just tells me your organisation is broken. You're absolutely right that you're wasting vast amounts of time, but…

No, you can either use the time-tracking, or you can not. If you don't want to use it in a project, remove the "time tracking" field from the project. Like almost every other field, you can't restrict its use with permissions. You can limit the use of worklogs with permissions though, which are one data item that feeds…

No, you have to do it one issue at a time. But iterating over a list is trivial in most languages that you might choose to do the REST API calls with.

Are there issues that could have been in two sprints on the different boards?

What do you mean by "serial number"? A serial number is usually a unique identifier for something, which, in Jira, is done with the issue key. So you already have what is effectively a "serial number" on screen. That makes me think you mean something else by "serial number" - could you explain what you would like to see in…

No, there's no comment I can see.

This usually means the back end service is not available. You'll need to talk to the owners/admins of the Confluence you are trying to reach, they'll need to restart it or otherwise work out why it's not available where you're trying to reach it and fix that.

I understand the frustration here, there's a loopy hole in the support process for the cheap/free accounts and you've fallen into it. There are problems that need back-end access to the services, which only Atlassian can do, so you need a support call, but you get pushed to the Community who don't have that access, and we…