Nic Brough -Adaptavist- Expert

Literally feed it a number. The rest API only takes numeric data (I thought it was milliseconds because that's what I see in code elsewhere). 4.5 is likely to be 4.5 hours, but you'll see that when you look again at the issue. Whatever unit it is expecting, it will be consistent.

Ah, the API is not listening in milliseconds. Have you tried plain 4.5?

On that page, there's mention of how you can do the same for comments.

Because for many types of issue (and process), "name" is the wrong word. As is "title". Bugs, Incidents, Changes etc - name or title are the wrong words for what the field does. Summary is probably the most generic thing they could have chosen.

We do need to get your urls fixed before we can start to look at broken comments and so-on. What url are you connecting to in the browser? What url do you have in "base url" when you go to Admin -> General Configuration?

My understanding of that doc is that you have to provide the JAR file for your IDPs JIT implementation. It's not something you just download from Atlassian because it's something the IDP needs to do.

What do you want to know about backups? The page you are reading mentions them and gives you a rough idea of the size of the backups you're going to end up with when you take a copy of the attachments and databases.

You can block them with workflow properties. See https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html but in this case, find the status that is "closed" (one or many), edit the workflow and add jira.issue.editable = false to those status (you might want to do the same for comments and other…

You could spend years trying to get this right, it's just as painful as trying to use a Jira database with SQL. You will need to work out every relationship and cross reference it all in a flat file that does not have any form of relationship handling mechanism (so learning XSLT and XML parsing would be your first step,…

Issue deletion rights is controlled at a project level, in the project permissions. Go into them and add yourself (ideally, do it by project role though). Admin rights means admin, not "can do anything". However, think very very carefully before allowing anyone to delete issues. Deletion destroys them and all their…

This is a Scriptrunner scripted field isn't it? When you configure it, you get a big box for the script and then a select list for template underneath it?

Read cwd_user for the list of accounts and most of that data. Join it to cwd_membership to see the groups (and cwd_group if you want to see the names of the groups rather than the ids)

What errors are you seeing in the logs? With h2 databases, the most likely culprit is that the database has failed, probably catastrophically, but we'll need to see the errors connecting in the logs (they're usually not direct, they won't say "it's corrupt", but give you more detailed errors that we can work out the actual…

I think Warren beat me to it - the guide he's pointed to shows you the urls you need to use and leads to authentication docs.

It's sort of the other way around - schemes don't hold projects, projects use schemes. You wouldn't "remove project B from a scheme", more "remove scheme from project" To do this, go to project B's admin section and change the issue type scheme to another one

There's the list of projects, but the system information page in admin is the place to look for stats. You may want to save a copy of (parts of) it daily to get some growth numbers out.

You're reading Server based docs for a Cloud system, click the "cloud" button to the top right to see the docs for Cloud

Yes, and yes - whilst Kanban doesn't care if an item is a sub-task, but in Scrum, sub-tasks are very much part of their parents. They will display on boards, but only as part of their parent. (In all cases, sub-tasks are in the same project as their parent, because they are part of the parent)

Change the template to number, that should fix the field.

Jira keeps a record of old projects so it can tie up redirects (when an issue is moved out of a project and then the project is deleted later). That data blocks the reuse of a project key There's no way to fix that on Cloud, as you need database access to remove the project key and destroy all the redirect (old issue key…

You will need to adjust the search that the first board uses, such that it includes issues from project B (note that boards do not belong to projjects in Software, they're separate views of a set of issues) Then you'll need to think again about sub-tasks. Sub-tasks are very much a part of their parent, not independent…

That is nonsense. What do you think "my local localhost" is? If you want to create a new Jira account, then do what I said before - log in as an admin and use "manage users" to add new users. Those are all the "steps". Log in, admin users, add user.

There's a lot to go though here. The shorter version is: >and thus there are a lot of custom fields. Why? Why are people not working with each other in similar ways and providing consistent activity and reporting? >When I create a dashboard widget [...] the dropdown lists all the available custom fields, even those that…

Could you enter it in milliseconds, as that's the storage format?

There is not enough information here for us to be able to help much. It is clear that you were trying to add a transition to a workflow. Past that, we're a bit stuck - what have you "messed up"? What did you try to do, what did you expect and what is going wrong?

Yes, but I think you already realised that. The steps here are just for adding data to an existing field across a swathe of issues, data that already has existing options in the field definition. It's not for creating a field from scratch. You should however find a flag that says "if option in my CSV does not exist, add it"

No, they need to drop off a board because otherwise they become clutter and eventually begin to break it. But, boards are only one view of your issues. You can search for issues on all sorts of criteria and get a full display in the issue navigator, go via the project reports, get them on to dashboards and so-on.

You can't. The issue picker field does not allow for it. I'm not sure about the number field though, I don't get that, field = 0 returns issues where it's 0 to me.

SQL queries are not going to tell you much - while you could probably work out something, the question really does become "what are you trying to monitor"? For performance, uptime and so-on, you'll be far better off using Jira's JMX interface to get information.…

You could fire up a new trial with your new one and just drop the old trial.