Nic Brough -Adaptavist- Expert

Yes, you'll need to upgrade your Confluence to a supported version. This is probably going to need you to upgrade Java, the database and possibly your operating system (your linux kernel is over 15 years old - that's not a good idea)

That's another way to do it, yes, but it's a bit clunky.

User macros are a widely unappreciated feature of Confluence!

Yes, you can create an automation that is triggered by "issue created" and has the "create sub-task" block as the action.

Ok, it was worth a look, as it's one possibility here, but I see Ollie's answer turned out to be the one! Something that might catch you out in the future though. Administrator rights do not mean "can do anything", they only give you administrator access. Project permissions are separate. It is possible to have an admin…

The burndown is actually working fine, the problem is in the way you are putting estimates in the wrong place. Sub-tasks are not sprint items, they are pieces of items that are. Because they're not sprint items, you don't put sprint estimates on them. Burndown only looks at estimates on sprint items. So the simple answer…

Yes, you can name them (or better, a role or group they are in) in the notification scheme for all events they should be emailed about.

No. The whole point of the updated field is that it shows you when the issue was last amended.

I'm afraid there's not a lot we can tell you here. You have tagged this with Bitbucket Cloud, which implies that you have set up something on Bitbucket that is trying to connect to a database, but you have not told us what you have configured, so we don't know what you are trying to do (it's not the core of Bitbucket Cloud…

Workflows in Team-managed and Company-manged projects are currently very very different things. Atlassian are trying to converge the editors for them (i.e. make "edit workflow" look the same, even though the underlying data is totally different), but it is a long path. In a TMP, you'll need to look at configuring each…

Great, thank you! I've thrown it over to Atlassian. They won't respond here, as they won't want to leak your admin's details, but hopefully one of them will be able to let you know what account still has admin on your system very soon.

The contact form is something your admins need to set up if they want to enable a quick way to find them. We can't do anything in the Community (we're not Atlassian, we have less access to your site than you do) other than ask Atlassian if they can identify your admin(s) for you. To do that, as I said, you need to tell us…

I'm afraid you might have lost everything here. It is not possible to have no other admins for the site, the software is hard coded to not allow people to remove the last remaining site or system admin. (It's possible to do it on Server/DC if you've got scripting apps, but not Cloud) If you really have no idea what account…

I know it's not what you were hoping for, but I'm glad we got you something that might be useful. I don't have a long weekend, I'm English.

Start by reading the application logs (in <jira home>/logs)

500 is a response error, it doesn't tell you anything about what went wrong on the server side. You'll need to read the server's application log to find out what failed.

Welcome to the Atlassian Community! It is actually seconds, but not just plain seconds, it's taking into account your settings for time tracking. With 60 seconds in a minute and 60 minutes in an hour, you can convert to hours by dividing it by 60 twice (or by a single division of 60*60) So, 43200 / 3600 = 12 hours. I think…

See https://confluence.atlassian.com/jirakb/how-to-add-an-attachment-to-a-jira-issue-using-rest-api-699957734.html

The field is "Responsible QA", but I'm going to guess that it's not on your "create issue" screen. You might want to try the "where's my field?" option in the configure fields option to the top right to find out why it's not there. My guess on the cause of the issue is that configuration of the field is * It is mandatory *…

Go to project settings and look for the "field configuration scheme". Go into that, and look for the "field configuration" for the issue type you want to make it mandatory for (there may well only be one field configuration listed, in the default spot) Go into the field configuration, you'll find it lists all the fields in…

Ok, could you try a quick test for us? Start creating an issue in project 1, and make note of all the first few fields it offers you. Do the same for project 2. These lists may have different lines (I'll explain later if we need to), but they will be in the same order. If they're not in the same order, we know that your…

Welcome to the Atlassian Community! Page properties are, as you say, probably the most powerful and useful way to do this, but yes, labels are another option. So, to answer this > Is there another way to display the labels that are used on each individual page? Yes. On server, you can write "user macros". One of these…

The obvious answer - use a shorter name (it's probably the full path, not just the name of the file) But we can't really help you much more with this problem, there's no information on what you were doing, the full error message or any context about where it appeared.

Ah, ok. The error is not coming from Jira, it's coming from the application you are using. We can't really help you with that, it's not an Atlassian system.

Which "app" do you mean?

Florin and Ollie already got the first two things to check. Third is: Has your right to create issues in this project been removed? Can you click "create" and check that you can select this project?

Welcome to the Atlassian Community! Could you give us the exact error (just the text of it, no need for a screen shot) and describe exactly where you doing when you got the error (I mean, were you editing the description inline from a view screen or card, or editing the whole issue, or transitioning it to a new status, or…

Where are you stuck in following the docs Fabio referred you to in the original question? Could you continue that conversation instead of raising duplicates?

On bad days, I feel like BO.B (old, battered, quiet and tired). On a good day, Waldorf (grumpy, realistic and sarcastic, but gets to laugh a lot and is surrounded by good friends)

There's no way to do this, the last updated date is always calculated from the last change made to the issue. I would not want to rely on the updated date to track if issues are being followed up on, people making notes, commenting, chasing or adding or updating the issue do not indicate that an issue is being dealt with.…