Nic Brough -Adaptavist- Expert

Log in as an admin, go to the project admin area to see what workflow it is using, go into edit the workflow, and remove whatever it is you've set to require the work logs.

What do you mean by "add a form"? Do you want the user to be forced to download a predefined block of text with gaps, fill it in, scan it and upload the image as an attachment? (That's how "assign a form to a person" sounds to me)

A Jira running normally (not with the flags atlas-debug sets) does not expose any debug functions, they're off by default. To debug a standard install, you'll need to run it with the same settings that atlas-debug sets.

I am not sure what you would expect from a "package". Jira, off-the-shelf, expects you to create projects for yourself, and configure them to meet your needs. The project templates do all that work for you, but they can't know what you want want to do with them, so they ask for minimal information and create a generic…

No, the simple filter view is done in code, not configuration that you can get to. It is intended to be very simple and part of that is not burdening the user with fields that might not be valid for the issue. To use epic link in a search, swap to the advanced view where you can search for anything

By default, Jira does not ask for work logs, your admins have set up your workflow in a way that demands it. You'll need to get your admins to remove the required work-logs from the workflow.

A Jira Server and a Jira Cloud instance are two separate systems with separate data sets. A Jira Server will not contain copies of a Jira Cloud system's data unless you have set up some form of synchronisation between them, and they will only use the same accounts to log in if you have set them up to use the same user…

Have you tried changing the sizing on the browser? (usually it's ctrl+ and ctrl- to change it)

No problem finding "issues in status X", but "date" is still not defined. Created, updated, commented, goes through a specific transition, and, and, and JQL has some useful functions around dates, but they can't work with "on a given date", they need to know what date you are looking at.

JQL is for finding issues, not reporting on them, it's not SQL. For your "group by", you need to be looking at the reporting method, not the question of what issues to fetch. Jira has a very simple gadget that does this, which you can import into Confluence. Run a search for the issues you want (project = XYZ and status…

For a one-column section, just don't use the multi-column layouts. This works in terms of how a page appears, but it is definitely not sections like the old editor because you can't break up your page into (single column) sections and move them around as a block.

What do you mean by "get out of a project"? Could you describe the problem you are having rather than a possible approach to fixing it?

To test this as closely as you can to the server, try logging into the Jira server and running the connection on that. If, for example, you're on a Unix-like system, a simple "wget https://marketplace.atlassian.com" will give you a decent error message you can use to chase down why you can't connect.

There's no alternative - if you want the power of schemes, then you have to be using a company-managed (classic) project, not a team-managed (next-gen) one

No, the whole point of JSM is that it is an extra layer of functionality on top of Jira. The first question has to be what are you looking for here? What are your requirements that JSM is not meeting?

It is, but I'd let the users do it for themselves. I would however build them an example dashboard to show them what they could build for themselves. There's a really simple trick to this. Most gadgets on dashboards work off a JQL query, and then report off the issues the query finds. So I often build dashboards that work…

Yes, that's entirely possible. As the admin, the best thing to do is create the projects and make one or more users of the project into project admins, then they'll be able to set up the boards to suit them.

It's not the event, I suspect you'll find it's the copy value function that is failing. It probably should be above all the other functions on that list.

So, you've not lost anything, you've chosen to discard it by not paying for the service any more. You will need to pay for the service you've been getting, for a little longer, then Atlassian will restore your access to it. Then if you want a copy of your data for when you stop the service again, you can create a backup…

Cloud Confluence doesn't have sections, it has layouts which come with two or more columns. The closest you can get to a section with a single column is to not use a layout in the block you want as a single column.

The create/edit permission also includes the ability to move pages, yes. It's not possible to stop people from moving pages if they can create or edit. With apps like Scriptrunner, you can write things that report on page trees, maybe having something that will compare each space with a known-good space and list…

That suggests your Crowd is read only or having other problems, you'll need to read the logs to see the full error message, which should tell you what the problem is. You haven't said if you are using an external directory for users, but if you're using the internal one, then the (embedded) Crowd will be logging to the…

No, there is no JVM monitoring in the Jira application. You can use JMX to get some information about the application, but there's nothing for the Java environment.

It is showing as enabled in Admin -> Manage apps? Are you following the docs for the Cloud version of it?

Nope, I've not looked at doing anything like that since Jira 4. If it's just cosmetic css and html, it wouldn't affect the performance. Recompiling bits of the core code does leave you unsupported though.

If Testproject is set to use the issue type scheme you show in the left of your screenshot, then I would guess that Bug and Enhancement are sub-task types, which can only be created from within their parent issue. You can't use the standard "create issue" to create them, and hence they're not offered by the selection field.

Yes, put customers who should see others requests into an organisation together, then you can enable the "see other requests from my organisation" for them.

Jira is an issue tracker. It has nothing to do with hyperledger fabric, whatever that is, unless the people involved with it happen to be using Jira to track something.

What SMS gateway system are you using?

What app are you using to provide test management? (if you are not, then can you tell us how you are representing test cases in plain Jira?)