Comments
-
You can't stop them adding people to roles without hacking the code. You can make it redundant though - make all your permission schemes and workflows dependent on groups rather than roles, and then it's just a bit of education for project leads that "roles do nothing". Of course, your Crowd/user admins are going to come…
-
I'm aware of Confluence Server systems (not even Data Centre, although I do keep nagging them) with millions of pages. Yes, running on hefty servers, but there's no need to worry about hard limits as long as your hardware can keep up with the load
-
> Tamper with the database. If you considered this one, please use this JMeter solution instead. ;-) Yes. Always. Tampering with a Jira database is an awful thing to do, and cleaning up the disastrous mess people usually make when they do it is even less fun. Thank you for giving us another way to do this!
-
There is a lot, totally. I think a better approach is rather than asking "what can SR do?", ask "what clever thing might I want to do that I don't seem to be able to do in plain Jira/Confluence/Bitbcuket/Bamboo?" That's how I learned it (and writing plugins, and Jira, and Pro-IV, and the rest)
-
Ok, let's skip over Confluence for now. It's the same sort of idea, but it's easier to concentrate on one at a time. The bits I've got from your last couple of comments are: > \JIRA\conf\server.xml file. ... I stopped the "Atlassian JIRA" service, and modifeied the server.xml Perfect. > <Context docBase="../servicedesk"…
-
I am sorry, I was not clear. The urls are valid, but it also means that the server on the other end of the url needs to respond to it. The servers you have given it do not appear to be reachable from the server you are configuring.
-
You can't do this directly. The code that does all the Agile calculations needs to use a numeric field, and numeric fields hold numbers, not lists. The closest you can get requires code: * Create a drop-down list with your list of values * Install something like Scriptrunner that supports calculated numeric fields and…
-
Ah, ok. That means what it says - the urls you are giving it for your other servers are not valid urls.
-
Ok, the docs for 7.9 are pretty much the same and make the same claim about improvements. I think this needs to go to Atlassian support!
-
Could you tell us what the log says at the point that this fails? <jira home>/log/atlassian-jira.log is most likely to contain the error.
-
I am sorry to say most of us here do not speak Korean - could you translate the text in the yellow box for us? (obscure or leave out any server details if you want, we're interested in the error text, not your exact settings)
-
You don't. The Next-gen projects do not (yet) support them.
-
Ok, that looks like you are having SQL errors, which suggest you may have a damaged database. This is not unexpected for the internal database (there's good reasons for the warning about the database type not being suitable for production) The next thing I would try is restoring from the last backup you took - if this has…
-
The mail handlers create the issues from incoming email based on the data in the email already, so I am not sure what you mean by "template"?
-
Who has "create issue" permission in the project?
-
I'm afraid the installers always ask for a username and password in order to create the admin user. You can't get through them without it.
-
There aren't any events fired by project permission changes. I guess the obvious question is why your teams would not know that an admin is making a change for them? Good admin practice would be changing permissions because a team has requested it, and after everyone affected has been told.
-
It find it easier to think of it as being in "modes". I log in with an account that has admin rights, but that just means an account that can do admin stuff if I ask. While wandering around in that mode, I can't (and don't want to) see everything. Switch into "admin mode" by hitting an admin function, and I can see the…
-
It should be in the "tools" menu when you have run a search for a set of issues or run a saved filter. Should be near the top right with a cog, tools or ...
-
Ok, we never said there was not a good reason or that it was a stupid user scenario. What I said was that it is locked down to prevent you taking down your system and potentially damaging your data. A better solution than downloading vast amounts of data is almost certainly going to be to look at why you're doing it and do…
-
I would lean towards a service - one that runs daily, early in the morning and runs a filter to find the issues that need updating based on their date. In fact, if it's a fixed date, you could run it annually and have it update them all in one go. It's still a bit of a load, but it'll only run once per issue and it'll just…
-
>In the scripted field, I get the current Date and compare it with a specific Date (ie Apr 1st) of the current year. If they are equal, I reset a custom field to be "0". Do not do this. A scripted field is NOT there to try to amend data, it is there to calculate a value for display (to answer the question though - a slight…
-
Sort of, but it's not going to help you that much. The issue field is sortable, but it's the full issue key, not just the sequence, so it has the project key as the first part. So, if you're going to try to use it for age, you could easily find project ABC first on the list when it's between CDE and XYZ in terms of age.…
-
Could you explain what this means to Sourcetree? As it looks unrelated to me, I suspect you've come to the wrong place though. Could that be the case?
-
The old code that is disabled by default was written before .xlsx existed, and Atlassian are simply not maintaining or updating it any more. So, while you can re-enable it with a flag, it's not aware of xlsx, and never will be (unless Atlassian decide to deal with the issues @Scott Theus has pointed you to, which I suspect…
-
Catch the "issue deleted" event (by listener or email) and use that to identify what needs deleting or flagging in your data warehouse.
-
No, it's not changed, you have to hack the code in Jira that does the layout.
-
Upgrade Jira 6.0 to 6.4, then to 7.0, then to 7.13. Then use Admin -> Manage applications to install a valid version of Service Desk Optionally, upgrade Confluence to 6.latest as well, but this is not strictly necessary (although I'd still strongly recommend getting it to at least 5.8)
-
If you don't have the subscription details, then you're not listed as a technical or billing owner, so you won't be able to renew. You don't get to see the licence at all in Cloud, it's all handled by the subscription details.
-
Here really - we're not looking for the whole log, just the bit where your login fails.