Comments
-
Partly - see the workflow elements in https://docs.atlassian.com/jira/REST/cloud/
-
There is a limit, but it's so high, your JIRA will be unusable well before you reach it. Yes, every custom field has a performance overhead, although the effects vary according to what JIRA is looking at the field for, each type of field has different overheads and it's not a linear calculation - you'll get a different…
-
No. Cloud and Server licences are different and separate things. If you've moved from Cloud to Server, you need to buy a Server licence for the applications, then you can stop paying the bill for Cloud.
-
Some, yes, but you'll need to ask Atlassian where they've been used, or have a look at the source code for details (if you have a commercial licence, you can download it for yourself)
-
Unfortunately, you did sign up for it. It's a monumental pain at times, and I'd love to have Cloud be more stable, with at the very least some warning of the bigger front-end changes (I wouldn't expect to be warned of changes orfixes that change icons slightly, move a button a few pixels or correcting spelling mistakes…
-
That's going to need a code change or add-on to adjust the interface, which you can't do in Cloud.
-
Reading the database is generally a bad idea, and the query you need probably depends on what user directory you are using. For most setups though, look in the "cwd_user_attributes where attribute_name = lastAuthenticated" is the starting point. Join it to cwd_user to get the user's human details like name and login.
-
When you try to move to a newer version, Confluence upgrades the data. The data for 5.10 is not valid for 5.4, so you can't just swap back. There is no downgrade route, you need to restore the data from a backup. I suspect your 5.4 is failing simply because it's finding bits of 5.10 in the data and possibly in the…
-
Did you restore the pre-upgrade data before going back to the older version?
-
I'm sorry, I don't have time to plough through thousands of irrelevant error messages. We need to see the log for what is going wrong, not spend hours looking at unrelated config failures (you should fix that as well really)
-
Your instincts and search abilities are spot-on, you have not overlooked anything as a tester or admin. As a developer, the SDK does let you fire up something resembling a test Cloud system, but it is purely for testing Connect add-ons and really has nothing to do with checking configurations for Cloud.
-
It looks like you have something in a transition function or field (provided by an add-on) that is not set up correctly. Could you have a look at all the fields that might be valid for this issue type in this project and check they're all set up ok, then check the validators and post-functions on the "create" transition…
-
You don't. Summary is one of the two fields in JIRA that are essential to issue tracking and hence it's not replacable (and there's no benefit to replacing it either)
-
Here is a good place to share, but the spam algorithms are still learning (it's only been a few weeks) One thing that might help is using a proper name in your profile though.
-
Vishnukumar and Danny have already said most of what I would normally say. I just wanted to add "do not edit the database". You've missed things, and it's a nightmare to unpick. You also now have a possibly corrupt and definitely unsupported database. Just disable the user and move on, it's not worth trying to force a…
-
I'm afraid I do not understand what you are asking for here. Boards have a backlog and active sprint view already, and they ask for a sprint length. I guess by a "sprint stack", you mean selecting the issues you want to commit to in the upcoming sprint? If so, I'm not sure what you're asking for here? It's already doing…
-
It does, yes.
-
I'm afraid that's only a tiny fraction of your log and it's not the part that is failing. As Brant says, you'll need to look through all the add-on starting parts to work out whihc one is faiing.
-
When you say the base url is the FQDN, does that url include the port 8080? Or have you stuck it behind a proxy that forwards from the FQDN to the actual full location?
-
Yes. But it's not a "include stuff and then arbitrarily exclude stuff later", it's "get the selection right". Change the filter so that it does not include the projects you want to drop. In some cases, probably including yours, the easiest way is to simply add "and project not in (abc, xyz)" to the filter.
-
Hmm. You say: The 'Resolution' criteria is as fundamental to filtering tickets as the above four criteria. Frequently, I want to know about search results for only open tickets; closed tickets are not relevant for current issues I'm searching for. This contradicts itself. If an issue has a resolution, it's resolved, and…
-
It's not going to happen - status is an integral part of JIRA, and hence is never going away. You can't run an issue tracker without the fundamental information of "summary" and "status". There are some tricks you might play with javascript or core hacking, but that status is going to come out everywhere. Your customer's…
-
The view screen will always show the system fields. So there's nothing you can do to hide it without messing around with javascript (always a bad idea)
-
I've relied on the simple brute-force way, making REST calls from test scripts with curl (similar to the apache client you sugget) - I had too many problems with internal tests on components returning a pass when it had really failed.
-
It looks like a botched attempt to "translate" the word Dashboard. You've checked the file system which is exactly where I'd start, but the translations are bundled up into compressed files - did you check those too? Also, do you have a developer tool like firebug you can use to inspect the raw html of the button? To see…
-
The best you can do is take a backup of the existing Cloud system, buy a new one (the $10 pm will usually be enough for most testing) and import your data into the new one.
-
Have you got the assignee as a field on the edit screen?
-
Yes, I've done it a few times. There's no "tutorial", it's a standard documented upgrade routine - just work through https://confluence.atlassian.com/adminjiraserver073/upgrading-jira-applications-861253088.html
-
You can't "upload" add-ons in Cloud. Cloud only supports the use of "Connect" add-ons, and the screen you have posted is the place that you "upload" them. You're really only uploading a connector that tells JIRA where the Connect add-on is hosted (if there is a remote element) and how to talk to it.
-
Mmm, you're not going to have a lot of fun with that - Clarity timesheets generally don't match with JIRA's time logging unless you have built a complete integration where Clarity is using JIRA issues as references for tasks. If you've got to that level of integration, then you're actually in a place where you should bin…