Nic Brough -Adaptavist- Expert

@Deniz Oğuz - The Starware- >Unfortunately un-licensed user is not anonymous once they login to your site" Yes, that's what I said. Once they've logged in they're not anonymous and you know who they are @Eddy Fras >a user can definitely login without a license on Confluence You can connect to it without logging, but once…

You will need to talk to your system admins, we can't help you here. We're a community of people here to talk about Atlassian and although your admins may be here, this is not the way to contact them, it's an open forum.

Boards are not containers for issues, they are a view of a selection of them. Done issues disappear from a board when they are done and the sprint ends - you don't need them any more, because they are done. The issues themselves are untouched, you can still search and report on them.

Bundled by what app? It's not a field that Jira provides off-the-shelf.

For Server installs, it's where-ever you chose to install it. For Cloud, it will go to the Atlassian Data Centre nearest the main users (usually based on the location of the person who signs up for the initial subscription) They have Data Centres across the USA (I'm not sure of how many or where without looking it up) and…

You might want to look at the issue collectors, they hand you a bit of javascript you can add to any web page that prompts a pop-up for gathering an issue. (Rest of my answer would be "what Joe said") I would not recommend using Epics for this though, they're intended to be massive collections of stories, and you're…

You'll need to raise it as a support request (I'm not an Atlassian, and there's no point me raising it when I won't be able to get into your systems to find answers to questions they may ask) The application link failure means you've got one or more application links configured to systems that are no longer responding when…

This is what it says it is - there's data in the database you're trying to connect it to. If you've started an install once and got as far as the first time it tries to write to the database, then it will have created enough data in there to cause this message if you run it again. Go into the database and drop the existing…

Server B is on the other end of a slow network connection, is running under-resourced, or is overloaded by poor configuration (possibly all three). Check the networking first, then server resources (how much memory does Jira have to run, is it on a decent CPU, is the server loaded with other tasks, is the home directory on…

Because an un-licenced user cannot log in. Un-licenced is anonymous, by definition.

The best thing to do here is define priority schemes and use them for the projects, don't use the default scheme for them.

This field is not a standard Jira field, it is almost certainly a field type provided by a plugin. It is pretending to be a text field as far as Jira's data is concerned, and then it is encoding data in Json and interpreting it as a set of fields when Jira calls its code to draw the field. When your code is asking the…

This will be something you've got configured in your system Start with a look at your history - is the change of resolution grouped with the status change, or is it separate? (If it is separate, then the users making the two changes may be different and that might give you a good lead) The reasons this might happen are: *…

I am sorry you are offended, but those are not my words, they are the words I found on the responses on the tiny handful of requests I could find asking for this (not "insane number" as you misrepresented it as) Before castigating me for being stubborn, could you please read what I've said properly? Your previous comment…

The internal API in Jira changes in each version as functions in the software are added and updated. In this case, your plugin is using a call that has been removed in version 8 (8 did a load of refactoring where deprecated stuff was removed completely). You will need to rebuild the plugin from its source code, after…

None of the underlying data is changed or lost when you swap - the hours you've entered remain on the issue, but the board starts working off another field. You can swap back at any time. Your existing issues won't have estimates though, unless you enter something into the new selected field.

You've set your workflow up to do something the business boards can't handle. The link you've got in that screenshot probably goes to https://support.atlassian.com/jira-core-cloud/docs/work-with-boards-in-business-projects/ which explains what workflow configurations break and hence hide business boards.

I wouldn't call it "integrate" because that doesn't tell you anything about what it is. I would look to the synchronisation apps that allow you to link projects or issues from one Jira to another so that changes on either end get synchronised over to the other. I've always used Backbone or Exalate for it, but there are…

Plain Jira does permissions at an issue level, not field. If you can see an issue, you can see all of it, if you can edit an issue, you can edit all of it. Roles, permissions, etc, irrelevant. Everyone has a common interface for the issue, there are a couple of "controlled fields", but that's it. If you want to restrict by…

https://scriptrunner.adaptavist.com/5.5.8/jira/quickstart.html is not a bad place to start, and I tend to steal liberally from https://library.adaptavist.com/ (even the scripts I wrote that made it there!)

Sprints and time estimates are two separate things. For a sprint, you will be doing that in the context of a board. The board has an estimation statistic. In many (most?) cases, that statistic is a simple number in JIra, but it is possible to choose the "time tracking" field as the statistic as well as all the other…

@JConstantine - I wish other people would answer my debugging questions as clearly and consistently as you have. Annoyingly, despite the info being absolutely what I asked for, it does not help. You have done everything absolutely right, and you've shown us what you've done which rules out everything I can think of that…

I would not expect any problem running the database server on that alongside the application server. Assuming it's only running those two services on top of the OS. See https://confluence.atlassian.com/jirakb/jira-server-sizing-guide-975033809.html if you want to see the recommendations for various scales of Jira.

There is no "jira confluence". Jira and Confluence are two independent (but often linked) systems. It is going to be easier to treat them as such. Let's look at Confluence first: * Download and install the latest version of Confluence * Run it, configure the minimum, but do not put any data into it, just get it ready to…

If there is no delete option, then the screen is in use somewhere. Could you show us an example of a screen that appears to have no delete option from the list of screens? 

If the field is on the view screen, but does not appear, then it is not populated. You'll need to check your code to see why it is not saving the calculation.

Subscription implies a Cloud system, but you've left it too late - you needed to pay for it within, or shortly after the trial period.

The only thing that matters to the licence code on any one server (or DC install) is that the number of login-enabled users is at, or lower than, your licence tier. If you're on a 50 user licence, you can have up to 50 people in your user list who are enabled and can log in (your user list can be longer, but only 50 can be…

You will need an automation or script to provide a post-function in the Epic workflow that will search through all the linked issues, work out what their current status is, and derive the transition(s) that each one needs to be pushed through to get them into the required status, then move each one of them through those…

It is not showing "backlog from another board", it is showing "issues that have been included in other boards". Boards are not containers for issues, they are a view of a selection of issues. If an issue is selected by more than one board, then it will appear in the card view or backlog as appropriate. If you don't want…