Comments
-
Absolutely - the REST APIs were originally designed for using the systems externally, not for add-ons (but it makes sense to use them for add-ons as it avoids re-inventing wheels) Have a look at the REST API tutorials and examples - you can find one-liners that use curl to poke a REST api and make it do almost anything.…
-
Yes correct. The list of plugins for OnDemand is limited, and does not include Behaviours.
-
Ahh, that makes sense. The "quick edit" pencil option only appears if you have the right to edit the field and it is on the edit screen. So you were blocking the user by disallowing their edit.
-
This is a bit of a long shot, but could you try this? Go to the issue as normal. Check that you do not get your pencil icon. Now click the "edit" option on the top bar to get into the whole issue edit screen. Is "assignee" on the list of fields on this screen? If not, then can you log in as an admin, find the edit screen…
-
See https://confluence.atlassian.com/display/DOC/Production+Backup+StrategyNote that it states that XML backups are only for "small installations" - 2GB is not small!
-
You should be using a full, proper database backup, not the internal backups.
-
Yes, help yourself. But bear in mind * You must not write to it (unless Jira is offline and you re-index after starting it) Risks: * Zero security - with read access to the database, a user can effectively bypass any and all security you've set up in Jira. It's only acceptable if your users can be trusted, or you have a…
-
I doubt that's relevant, as it's a bug in an older version, fixed in yours. What does the log say at the time you try a search? The best thing to do is have two sessions - one browser window ready to click search and a terminal logged into the server and running "tail -f atlassian-confluence.log". Click the search, get the…
-
What does the log say?
-
Sorry, what .jsp file? If you've lost access to attachments, you need to check that the files exist on the disk, are read/writable for the confluence users, that the attachments are referenced correctly and then read the log file to see what the errors are. What error message are you getting when you try to access the…
-
Pretty much. The only thing I'd change is the last bit - when you create the new field, put it in both the dummy and target project(s), or even make it global. One less step basically.
-
Create a dummy project that uses the field. Create CSV with two columns - summary and field value (you can use the same value for each line!) Import the CSV into the empty project - it will create one issue per line, and, if you configure it correctly for import, create a new option for each one in your new field. Delete…
-
Nope. You can run a full export, but it's going to end up on the file system on the machine you can no longer log into. You really need to get access back on that machine, sorry.
-
Probably not. You've not described your setup, so we really can't tell you much. All we can do is give you the principles - you need to get a copy of the database, and you need a copy of the attachments. With zero useful information about your setup, that's it, nothing else I can say might be useful.
-
That's the way I would approach it, yes. A script that could pick up a user entering "not planned" and think "ahah, they mean fixversion = empty". That wouldn't affect any of the core behaviour, you wouldn't need to hack anything, just write a plugin to provide it, and "fixversion = empty" will still work properly.
-
Ugh, no. "field is empty" is a standard JQL phrase and really does mean "field is empty". To change it, you'll have to hack the JQL language to make one specific field understand that a different phrase means one thing. If you really do decide to do this, then PLEASE do not remove the "is empty" from the field, the vast…
-
What does the log file say just before the "JIRA is locked" error you get at the end of the startup?
-
Use a later version of JIRA and Java is almost always a good answer to performance issues
-
Ok. However you do that, bear in mind that 1) JIRA works on a single datasource. You can do what you want behind the scenes, but it must look like a single datasource 2) It's very rare that the database is the problem when JIRA starts to creak. The bottlenecks are usually in the index and application server.
-
It's the number of active users on licences. I've no idea what you mean by "scale the database".
-
The bad news first: >Is it possible to scale JIRA in a cloud (AWS) No. >is it possible to modify database schema? Absolutely no, it has no idea of how you'd handle separate tables >Is it possible to separate JIRA in a web server and multiple database instances with replication without additional costs? Nope, it doesn't do…
-
You need to delete the user from the directories, not JIRA This will leave orphaned data though - you'll want to bulk-edit that to fix it.
-
That will work fine, as you say, just remove the two accounts from the directories you don't want them in.
-
There's been a LOT of complaints about the recent release (try clicking "questions", then "popular" here to see that 4 of the 5 highest questions are about this) Atlassian have pulled it too - if you go to "download", you'll end up with 1.7 instead of 1.8 now.
-
It sounds like you aren't following the installation instructions to be honest. As Matthew says, greyed out options in BigGantt tend to mean you haven't set it up. For BigPicture and Gantt-Chart, "don't show" and "can't find" suggest that you aren't looking for them as per their documentation.
-
I'd recommend explaining "buggy" first, as we might be able to help you with that. Frank Polscheit's Gantt is the one I tend to try first when asked about Gantts as well, that might be worth a try for you too. Portfolio is not a Gantt chart though. It could also be a much better option than Gantt charts for you because of…
-
Go to the manage dashboards option and click the yellow star next to the one you want to get rid of.
-
Status and project are mostly irrelevant here. Create a security scheme that has at least one "level". In that level, name the three managers (or, better, a group, or best, a role that only they are in in each project). Apply the scheme to both projects and set the security level on those two issues.
-
Yes, give the project a security scheme and then set a security level on the issue you want to hide, (assumes you've set up a level which includes and excludes the right people) I think you mean you want to prevent users creating, using or seeing an issue type though. That's not possible natively and even the add-ons that…
-
No, they're a project level scheme.