Comments
-
The gadgets take their url from the base url, there's nothing in the gadgets to change.
-
Ok, you may already have it then, but in case you do not, go find the server.xml file in the /conf directory in the Jira installation. It should have a line in the "host" section saying Valve with a value that contains a class name and AccessLogValue. If it is enabled, or you enable it, then you should find access logging…
-
It depends on your setup. Are you just using Tomcat, or is there a proxy between the server and the users?
-
You don't do it in Jira. Jira relies on a specific structure in its home directory. So, if you want to locate parts of the home directory in different places, you have to do it with the operating system. The most simple solution is to move the /caches/indexes to another disk (remembering that they must be fast local disks…
-
The only unusual thing I would worry about is that the proxypass should be pointing to where the Jira is actually running, not the proxy. If they really are running on the same server, then try changing it to the ip address or localhost
-
I am sorry, I can't get you any further - the only stuff I have written for Cloud Jira was on the back-end, post-functions to update things, and they were in ScriptRunner, so I did not need to think about most of the interface.
-
Start with a look at the column mapping for the board. You need to ensure that all status are mapped into a column for the issues to appear on the board (and hence in the backlog).
-
You will need to have put logging in place before they made the change, and ensured that logging was catching the ip address. If you did not have that set up, then there is no way to know what the ip address was.
-
No, none of that is right. A field is an object that defines how you add data to an issue. A field has a name, a type and some other stuff that defines it and its behaviour. For now, let's call that the field header. If you change any of these definitions, that is logged in the administrative audit log. Then there is the…
-
They are updated when the user changes them. They might do it with an edit, or during a transition, or by triggering an automation or script, etc, and they could be changing almost any field in any of these. Most of the options come back to how you have configured your Jira workflows and automations and listeners if you…
-
I think I use a range of tactics and tricks. My favourites though are * Making it clear that if I add their (pointless) field to their project, inflicting it on everyone else, then they will get the other fields other projects ask for. Because you're all supposed to be working in similar ways. * Get the main stakeholders…
-
No, hang on, I've misled you. * The audit log is tracking configuration changes, such as the creation of and changes to the field, as I thought you asked in your comment. * The history items are tracking changes to issues, including changes to the values of fields, as suggested by your question. I should have made that…
-
You will have to download both sets of data, load one into a dev system, use merge tools and project import to merge the other one in, then export it and upload it into your target Cloud system, overwriting it with the merged copy.
-
Remove their right to "create issue" in the projects you want them to use via the portal.
-
It does mean every project needs its own scheme, if you use groups directly. However, if you set up a permission scheme that says things like * Browse - role:developers, role:users * Can be assigned issues - role:developers * Work on issues - role:developers and so-on, then you can do stuff like: * Project AAA, Alice is a…
-
They release irregularly and often, there's no fixed schedule, and the updates are released whenever Atlassian think they're ready. Follow https://confluence.atlassian.com/cloud/blog for the weekly updates.
-
The custom field header is only tracked in the audit log.
-
Markup has changed since the original question.
-
Could you check a couple of things? First, where is the "Done" status mapped in your board. Second, how many story points are on HOS-1714? (Just that issue, not its sub-tasks or linked issues)
-
My guess is that your status X is not in the "done" column in your board. For an issue to be "done", it must be in the right-hand column.
-
If I understand it, no, you will need to go back and delete the .dat files if you don't want them any more.
-
You need to put a "transition screen" into the transition that the validator is on to ask the users for a Team during the transition. The screen only needs to contain "team"
-
I think you answered your own question here over at https://community.atlassian.com/t5/Jira-questions/Where-does-Jira-store-the-highest-ID-value-for-entries-in-table/qaq-p/852192 !
-
I don't think they will. Cloud is a set of services running on Atlassian servers, the server and DC versions are run on servers. Most of the world simply does not use Macs for servers, so 99.999% of the market is going to be either for Linux server, or legacy Windows ones (Given Windows is now running on less than 13% of…
-
What exactly are the memory errors you get, and is there a trigger? For example, it happens when you run an export or a particular board? Don't just try throwing memory or resource at this, you can make it worse if you don't know why you're doing it and how it might improve.
-
Your best option is one of the scripting or automation add-ons. ScriptRunner and Automation both have "transition issue again if xxx" functions built in, so you don't need to code anything.
-
The scripting add-ons can provide a place to write code if you don't want to write your own add-on to give you a post-function or listener to do it. Otherwise there's nothing internal to do it.
-
I would roll back the changes you've made to the last good backup, as hitting the identity column is a disaster and could have done all sorts of damage. Once you've got a reliable database back though, yes, you have the right idea if you want to do this the bad way (You should never never write to a Jira database. If you…
-
No. When you import, each line is an issue. Jira only has two options - import new or update existing. There is no "randomly ignore lines". If you don't want to ignore something, remove it from the upload file.
-
I would not do that. It's a little clumsy to do physically, but the main reason is data and reporting. If you move an incident to become a change, there are two big problems you cause. 1. Incidents and Changes usually have very different data. For example, a change has no use for "root cause analysis" and an Incident has…