Comments
-
Components are multi-select fields in terms of data, so they're storing and enabling search and reporting in the same way as a custom multi-select. But components are a "system" field that have additional functions - a way to type instead of select, the ability for project admins to maintain the lists rather than Jira…
-
Welcome to the community. You have not explained what you mean by "design", but I think I would guess that one of these sites is on Cloud Jira and the other on Server (or Data Centre) Jira. Cloud and Server do the same things and have very similar underlying data, but they have a very different layout (design?), with…
-
This isn't going to happen in any sane way. "Extract all" is hard work and a vast waste of your time. Coding it is going to consume far more money than a look at add-ons or reporting tools, and be nowhere near as flexible, maintainable or useful. You would be better off doing a proper analysis of what reports your…
-
Atlassian support only do direct support by a human if you have the Premier Support option. All other support has to be done via the support desk (although they will then get in direct contact if it is necessary). If you have a "starter" licence ($10), there is no support, you will be directed here to the community, where…
-
I'm running Jira and Bitbucket fine on a server with only 6Gb RAM. They're for a small number of users, but quite old, with not an insignificant amount of data. How many users, issues, repositories and code do you have?
-
Bamboo is only supported on the platforms listed there.
-
You will need to hack the core code that lays out the screen in Jira - that is not a trivial thing to do and it makes upgrading harder and renders you unsupported, so I do not recommend it.
-
You need to go from 6.1 to 6.4 to 7.0 to 7.target. Do not skip either intermediates step, there are a lot of known problems (for example, priority settings break if you go to anything above 7.0 from 6.anything)
-
Is the payload of your AJAX call identical to the POST?
-
You can't do this without re-writing service desk. The request is intended to be a simple single page for the customer to enter all the information asked of them.
-
I'm with Linda on this one - the whole point of the internal comment is that customers do not see them.
-
The trial status does not matter here - you put data into the system during a trial, then that system would have been re-licenced as a production system (there's no difference in functionality, only access). Unless you set up a new system on a different url? If the data was entered during the trial period in the same…
-
See https://confluence.atlassian.com/bamboo/supported-platforms-289276764.html
-
As a technical answer to the "how long" on Atlassian's side - you fill in the form to get a trial and allow a day for it to arrive. Most are done and ready for you to log into in less than an hour in my experience. After that setup of the empty system, then you need to make your time for what Joe has said.
-
Do you mean if Bamboo is supported while running on SAP JVM, or wither it can run a SAP JVM for build/test?
-
Click "add existing request type" at the top right of the screen.
-
This suggests the applications are failing somewhere (although not the Tomcat running them). What does "the browser cannot connect" mean here? You get an error? It sits there with a blank page for ages and then gives a timeout? It just churns until you close it? Logs to check are <application…
-
Be aware that also Some people can think clumsily and script stuff over http (don't do that, it's clumsy, push them to use REST instead) A lot of REST calls attributed to accounts can be coming from functions in the Jira UI. When a person visits a Jira dashboard for example, each gadget that works with issue data runs a…
-
You can't, sort of - the list you see on the create screen is the list you have in the "issue type scheme". If you don't want those issue types in your project at all, this is easy - edit the issue type scheme and remove the ones you don't want. If you need them, but don't want people creating them, you have a problem,…
-
A dashboard is mostly built from saved filters, which can select issues from many projects. People often use dashboards to get broad views of what is happening across some or all of the projects in Jira. There are some reports available on dashboards that don't even look at issues, it's a broad place for people to build…
-
You will need to read the log file (<jira home>/logs/atlassian-jira.log) to see if there are errors occurring when you click "save"
-
No there's no field permissions, VTS must mean that the account running the REST call did not have "edit issue" rights. What error are you getting and what type of field is it?
-
What does the log file say the error is?
-
A board is a view of a selection of issues, that you can use to see and update them. It displays them in columns, with each column representing a step in your process for them. A dashboard is a place to collect together a set of reports that people might find useful. They don't have a lot in common, other than they both…
-
You lose a nice simple text-based markup, but you will gain: * An editor closer to WYSIWYG * Speed * Security (3.x should not be allowed on the internet, it leaks too much personal data. For security you need to be on 6.12 at a minimum, and that jumps to 6.13 in a few weeks - please, go to 6.15 asap) * Closer integration…
-
It is good that Cloud finally started to allow Conditions and Validators, even the weaker "but still can't check input like Server has been able to do since Jira 2". But a 3-year-old conversation is the wrong place to talk about it.
-
I think you need ContentEntityManager.removeContentEntity( contentEntity )
-
There's no real tutorials I think are any good for free, but I've learnt scriptrunner by reading public scripts and adapting the bits I need. That was a long time ago and since we (Adaptavist) took it on, we've been trying to build more help for using it. https://learn.adaptavist.com/course-library has a course for getting…
-
There's no way to do that, you'll need to buy a Jira Service Desk licence, and let the Software one lapse.
-
Before answering a question, read it carefully in full. I've made the mistake more than once of answering a long question where there is something buried towards the end that would change my entire answer, or approach to it. Ask for clarification if you are unsure (annoyingly, you have to do that as an answer in this…