Nic Brough -Adaptavist- Expert

Same as you asked the other day - see https://community.atlassian.com/t5/Jira-questions/Explain-how-to-make-a-field-non-editable/qaq-p/1474358

I suspect you've found an app for Server Jira. These cannot be installed on Cloud. For SAML authentication in Cloud, you will need to get Atlassian Access 

They're "yes" differently? That makes no sense. Could you tell us the difference between their usage and yours?

So what are they doing differently to you?

It's a botch which creates a parallel sprint process that will not work. It creates a field that lies about whether a sub-task is in a sprint or not.

What searcher have you selected for it? (Admin -> Issues -> Custom fields -> Your field -> Edit)

What are those few users doing differently to you?

This is the sort of corruption you can get when you nest home inside install or vice-versa. Your database is damaged, and you probably need to re-install and recover from a recent backup.

Changing the path is the wrong answer here. You need to re-install or move the directories so that they are separated out. Otherwise you will have problems with your installation, possibly ending in total corruption of your database. You must never put the install inside the data directory or the data directory inside the…

No, you have a developer licence for 100 users. That can be used in a test system if you choose to build one.

Your account that Confluence is set up to run as does not have the right permissions to use the java installation. My best guess is that you installed everything as user A but are trying to run it as user B (And as it is a re-install, you might not have cleared everything out properly while A was trying to install it, so…

No, you can use it with any git repository you want. What errors are you getting when you try to connect to your repo?

My original advice remains the same - your javascript simply will not work during bulk-edits, you absolutely need to be doing the validation with validators (bulk edit respects validators, but, rightfully, not javascript) Your client needs to understand that if they want this validation, they need to get an app to provide…

All issues have an assignee field (unless you deliberately disable it). This is the person who is currently responsible for getting the issue dealt with. So use that field to hold who the current responsible person is. If you have others that might be useful to know about, draw them in as assignees on sub-tasks, or name…

Ok, that's pretty much the answer to the question. Your account does not have access. You'll need to talk to your administrators about (re)gaining access. (Or, the other reason is the account expired as it was not renewed - again, your admins are the ones to talk to there)

Ah, ok, you'll need the older version of the doc - still the same thing, you'll need to get an Oauth token.

You don't get system-administration in Cloud, only Atlassian can be in that group and be that level of administrator.

Remove it from the "edit" screen. See https://confluence.atlassian.com/adminjiraserver/project-screens-schemes-and-fields-938847220.html and concentrate on the middle path in the first diagram If the field is not on the edit screen, it cannot be edited by the end user, but it can still appear on view screens, and in search…

You'll need an oauth token - see https://confluence.atlassian.com/adminjiraserver/integrating-with-oauth-2-0-1013845729.html

The creator of a sprint is not logged.

The breakdown chart you describe is nothing to do with burndown, so I'd expect to see them separately.

And, @Andy - PTC Redundant , despite the assumptions people make, the level 10 person is not who you might expect. I am an obvious candidate, but level 10 is not just about longevity and volume, and my contributions only match part of the criteria for it, not all of them. Heck, I don't even have level 9, which tells you I…

I suspect there is only one sprint here. Sprints do not belong to projects, they're a function of scrum boards. Could you confirm where you are looking so that you see "each one has different stories"? Also a quick cheat on debugging this, could you got to Issues -> Search and start to type "sprint = <name of sprint>" - as…

Automation could do that if your Perforce service accepts http REST calls from other systems. If you need to run p4 commands though, you'll need one of the scripting apps - Scriptrunner or Powerscripts for example. They're not free, and there's no properly supported or reliable free alternative other than writing your own…

The link I gave includes "how to send a query to Jira over REST and get a response of a list of issues". Try expanding the "issue search" header on the left of the doc. For your new query, the search becomes "project = x and fixversion = y"

Ok, the simple thing here is that you do not put Scrum estimates on sub-tasks. Burn-down is exactly what you see here - all or nothing on each item you committed to doing in the sprint (not the subtasks)

You can include the sprint field in exports. I can't find an insane number of questions or requests on the internet for this, I've found a few, all of which have been answered by pointing out that the reason behind doing the export is a clumsy and pointless process. If you use the tool as intended, you don't need it.

Have a look at the "search" section of https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ - a search for "project = x" will do what you need.

Could you explain what you are talking about when you say "where is other" and "other is nothing"? As for "I want to add subtask as burndown", I think you're misunderstanding what scrum and burndown are for. You do not burn down on sub-tasks.

I don't think there's any pedantry here. Issue is not a great word, but it's a lot better than all the other suggestions I've seen (for example "ticket" can go burn in hell - it's not a "ticket" unless I've got a token of some sort in my hand that shows that I'm entitled to something, which is not what 99.999% of Jira…