Nic Brough -Adaptavist- Expert

I would say you should find a simple project that you would like to do, work out what the best language to do it in is, and then give it a go, starting with the tutorials and guides you can find for that language. Before getting into any particular language though, I would take a run through one of the visual learning…

Yes, a service that is designed for large files is the answer. You will in fact get a more accurate "count" from a file service because in Confluence, you can't tell if a file was successfully downloaded or if it were just viewed rather than downloaded. I don't know what Atlassian use to serve up their installation files,…

There is no way to do this other than create the same fields and options separately.

There are no layers in the customer functionality. You're either a customer (in or outside an organisation), or you are not.

You need to log in as a Jira (or Jira System) admin, go to Admin -> Issues -> Custom fields, find "Problem Area" and look at its "context" (there may be more than one - each context has its own list of options). You'll find the list of options in the context.

No, there isn't a way to do this. The standard advice is that you should be using only a few global roles to try to keep it simple for your project admins, and try to use generic names that are useful across projects. There's an explanation and discussion over at…

But project-local roles are just as confusing and work even worse than global-project roles. The global roles simplify things. The problem there is that a project-local scheme just shifts the complexity from "that role doesn't do anything in this project" to "I don't know what this role does in this prohect and I need you…

Could you define "not working"? Error message from Jira? Service not responding? Browser error? Login screen, but it won't let you log in? What steps have you taken to identify the problem? What do the logs say? What have you done differently from what the documentation says?

No. A sub-task is part of its parent, which is in a sprint already. It is nonsense to have a sub-task in a different sprint to the one it is in because it is part of a parent issue.

What do you mean by "support export schema file (project config dump) XML file"? Do you mean a standard "backup" xml file? Or some other type of export/dump/project/plugin-export thing?

JQL returns a list of issues, nothing else. It is up to your reporting to read those issues for their field content. You'll need to tell your Confluence's Jira macro to read the "project description field" (assuming you are using the Jira macro)

What do you mean by "add it to my web site"?

If you remove the fields from the "edit" screen (and possibly create if you are scripting them), poeple will not be able to edit them.

"Problem Area" sounds like a custom field. You will need to ask your administrators for new options for it.

It is not very clear what you have set up or how, but looking at "not present in edit screen while showing in view" alone, there are two widely used way to do this * The field is on the view screen but not the edit screen * The field is read-only in some way - a scripted or derived field, or literally a "read only" type…

Text fields are not "statable" - a computer can't know whether any entry is supposed to be unique or not. They have to assume that every text entry is unique, so gadgets that report on them are essentially useless, as every value could be different. A pie chart based on a text field simply needs to show a series of 1-sized…

I think you have misunderstood what Jira means by an "active" and "inactive" workflow. An active workflow is simply one that is used by one or more projects. It's active because it is used. Create a classic project of any type (not a next-gen, they don't have conventional workflows). You'll see Jira creates a default…

The javadoc is not supposed to be a developer's guide, it's a practical usable reference doc. If you want development guides, check the Atlassian plugin writers docs.

You'll need to tell us what other app you have to provide scripted post-functions if you have not got ScriptRunner.

No, you should never edit a simplified workflow. Technically, in the background, a simplified workflow is a standard workflow, so it looks like it can be edited or used by projects outside the board that it is for, but: * All projects included in the board must be using that one single workflow and no others (change that,…

No change for me, this is my usual stash. I make up my mind if I'm drinking tea or coffee at breakfast and tend not to swap during the day.

How have you connected the knowledge base to it?

I've done something like this years ago. I used the Jira SOAP interface, but nowadays you would need to use the REST API. Your QR Software should be able to identify the Jira issue from the QR data and issue a REST call to Jira for "perform low stock transition". I can't help you with the QR software, you haven't said what…

The only one I've seen is https://marketplace.atlassian.com/apps/7070/jira-client?hosting=server&tab=overview

That's not a Jira Service Desk app, that's an app for Jira which supports JSD. Have another look at the list, I think you'll find it's listing all Jira apps valid for your version of Jira.

Just to support Jerry here - only Server and DC have Priority schemes. Cloud does not, and last time I looked, the request for it had been shut down with "won't do"

No, there's no way to do it. Sprints belong to their boards.

Are the tasks that are "done" in the very last column on the board when you close the sprint?

> I see that after DONE we have a column called: can't be fixed. Maybe that's why. Can I just re-order columns? Yes, that is the problem - the last column on the board is what Jira sees as "defined as done". Re-ordering your columns so that the last one contains the issues that are "done". At the moment, your "can't be…

There is nothing for Atlassian to fix here. You might need to fix your board configuration though. The issues being added to the new sprint are added when you close the last sprint with issues that are not "done" (they and all their sub-tasks are in the last column of the board)