Comments
-
You will need to add configuration to the server.xml as the error message says. See https://confluence.atlassian.com/jirakb/jira-server-startup-fails-with-tomcat-misconfigured-error-958453799.html for the details of what needs adding
-
There's no way to do this. Jira simply considers the last column on a board as done.
-
There's nothing more than all the standard reporting. Generally, it sounds like you should start with a filter for "issue type = defect"
-
Because you have set up an automation or script to set the approval automatically. I'm afraid we cannot tell you about your process and how it is configured, we have no access to your system to look at it.
-
You will need separate user access for both, although, if you are using an external directory such as LDAP for your Server, you could get Atlassian Access hooked up to it, which can then make them available for Cloud
-
Copying data around like that is hard work and pointless. The licence scheme is designed to allow you to take your "evaluation" system and convert it to a "production" system, with everything intact very easily. You just apply the production licence to it, and it's now production.
-
Welcome @Singh Neha Could you explain what you mean by "connect"? I ask because you've tagged this with "cloud" which suggests that you are trying to do some form of reporting in Jira on a remote Mongo database (On Cloud, you don't care what the database behind Jira is, you don't get to see it) If you mean use Mongo as the…
-
Could you describe "cannot download"? Is it not visible in the attachments? There but there is no download button? The link does not preview? The download button on the preview does nothing or isn't there? Download starts but fails? Is there an error message?
-
No, the templates only matter when you create the page, they're irrelevant after then. Some people add page properties or labels to templates so that they can track them, but people can remove those as they edit a page.
-
Anything can run JQL - see https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#searching-for-issues-examples - you can almost paste your JQL into there for a working call. To get it into Confluence, you will need to find something that can make the call, and more importantly, format it usefully.…
-
The list of available issue types is determined by the project you are creating the issue for. Boards are a view of a selection of issues, they can't determine what you can create.
-
This can happen when you are missing the "assign issue" permission (or it's not on the edit screen) on any single issue in the list of issues you are trying to reassign. To test that, find an issue you can re-assign and note it down, re-run the bulk edit, but deselect all but that issue. Does it now let you change the…
-
Ah, ok, that makes sense, it is working as intended. The point of the resolution field is to tell you whether an issue is "unresolved" or "resolved" (which could be any string you want, ideally one that describes why you think it is done with) So Jira always displays this field. When the field in the database is empty, it…
-
* Simplify and housekeep - there's a lot of performance tuning tips out there, but the main things you can do is avoid fielditis (limit the custom fields, resisting "we need a new field" requests, share them as much as possible, and limit their context), share workflows and other configuration, clean out what you're not…
-
For a proper HA system, you should move to Data Centre. The best you can do with a Server instance of Jira is a warm-ish standby. Two machines, one of which is production, the second a failover system which is not running. You replicate essential data to the failover system (so probably putting attachments on a shared…
-
This usually happens when someone places the resolution field on the create (and/or edit) screen. You should remove the resolution field from all create and edit screens. I would also strongly recommend not have "not solved" as a resolution, it is probably inaccurate and definitely confusing. If it means "needs work" then…
-
There is a very tiny overhead in using many scripts, as Jira has to handle each as a separate post-function. But, you will usually find multiple ones easier to write, understand, and maintain as requirements change. So, I would look at each requirement and group them by what they are for. If, for example, you have three…
-
Please see the discussions above.
-
It is possible, but it is painful, and can easily cause performance issues. Jira's database is absolutely not built or intended for any direct reporting. The JQL you've given us as an example requires 8 joins, just for a single issue type, and that's probably an underestimate as I've only looked at the basics of the…
-
But you want to count them as "done", so they need to be in "done". It's a very simple question - are they done or not? I suspect you need to track UAT separately from the rest of the work, in which case you don't need things in UAT on the developer board. (I'm not sure what you mean by "lanes" - do you mean swimlanes?)
-
Are you choosing Next-gen or Classic? What do you get asked after selecting one of the two?
-
There are a lot of things that could cause this, from (transient) network errors through to server-side bugs. I assume there was nothing else on the error page when you got this "error processing"? If so, then I am afraid you need to start by reading the logs for the Confluence application to see what the error was on that…
-
Could you tell us what type of field "Engineering" is? The part-faded screenshot makes it hard to work out what it is showing.
-
I was about to say almost what Jack said! I think my grasping-at-straws "look at quickfilters" is firmly ruled out as the problem.
-
An issue must be in the last column of the board to be defined as "done", and "done" is what Burn-down and velocity work from. It sounds like you want to measure the velocity of the development team separately, without taking account of the whole cycle of an issue. I am not sure if you want QA separated out from…
-
You can paste a new licence key for the right version straight over the top of the incorrect one. If you have bought the wrong licence, get in touch with Atlassian immediately, they'll be able to refund/reissue the right type of licence.
-
How are you "referring to another issue" in the new issue? How are you using "text box to search another issue"?
-
There are no restrictions on doing this, Jira doesn't care if you log in several times from different sources. I can't speak for any apps that might object, but I can't think of a reason that they might be checking sessions and doing something differently to Jira. You may find some temporary discrepancies if you are using…
-
Log in as someone with permission to create projects. Click "create project". See https://confluence.atlassian.com/adminjiracloud/creating-editing-deleting-and-hiding-projects-844500729.html You'll find mention of permissions as you follow that.
-
You cannot do this at all in plain Jira, an issue is visible in its entirety, or it is not. You can't hide bits of it. With an app, you'll need to write a whole new attachment function to handle this, I can't see a way to inject hiding into the attachments.