Comments
-
Yes, it has not changed.
-
What errors are you getting?
-
I can see why the conversations above get complicated and unhelpful. I think you are very very close to fixing it, but missing how to extract the fix from our conversations (because we barely mention it, mostly we're talking about how stupid a design flaw it is and why it's hard for Atlassian to fix it and actually how few…
-
Yes, the search functions will let you find issues that match the first question and the Software reporting the second question.
-
I think you should take a look at how prioritisation works. This problem affects two types of people - inexperienced admins who have not seen it before, and experienced admins who are cleaning up after others. On top of "only a few people affected", there is a manual fix. Less than ideal, it's a bit slow for the few…
-
Actually, it won't make any difference on the back-end. The underlying "this is how we store, index, search and work with custom fields" has not really changed. However, one way to make custom fields more performant has always been to limit their context - a field that is only for project X (or several projects) is more…
-
We don't know where you might have put them. The backups you take from Cloud are your responsibility.
-
It helps if you ask a question, or explain where you are stuck, rather than make a partial statement and then repeat it in the description. I have nothing to work with here.
-
The list of available issue types is determined at the project level, you can't do any of that.
-
That's annoying for the end-user - presenting them with fields they don't need on an issue type is not friendly, and a good admin will keep the fields as simple and clear as possible to save them time! On a technical level, many fields is one of the ways you can cause issues. Performance is quite a complex thing in Jira,…
-
You cannot do this. Listeners have no way to talk to the front end, and they're too late in the issue create/update process to actually ask anything of the person triggering them.
-
There's no way we could know that because you did not give us the context. Anyway, it's not the problem, we need to see the error lines.
-
You'll need to write code to do this, because: * Jira doesn't have negative reporting, you can't ask to find issues that aren't there. * Your report is nothing that Jira has defined * There's nothing to send reports by email (manually or scheduled) * There's nothing to catch and respond to the incoming emails I would reach…
-
There's two ways people do this. The messy and annoying one is to implement SSL in the Tomcat Jira runs on. The better, easier and more flexible one is to run it behind a proxy that does SSL. The usual one is to use Apache for this, but you can do it with others like Nginx, Lighttpd and so-on. See…
-
Partly. Some of the badges are automated, some are manual. The automated ones have simple rules that the community software can be given easily - x posts in y category for example. Have a look at the profile of a community leader, read the badge descriptions of what they have, you'll see those rules in English. The manual…
-
You'll need to explain what TDS is, and what you're trying to do with it.
-
I've not seen one, but I would use one of the scripting apps to create a listener that spots "file attached" and duplicates it out to the shared network location.
-
It depends on what you want from it. The core of a service desk is an "issue tracker", so yes, you can build a service desk on plain Jira. But the stuff around that is not what issue trackers do - portals, SLAs (defining and reporting on them), agent queues, simplification for end users, etc. You will need to do a lot of…
-
Ok, what is the collation type? utf8 ?
-
There are several, but it is dependent on what you want from your scripting tool. Scriptrunner is the most powerful, with scripts that make direct calls to anything Jira exposes as an API, and pretty much any code you want to support those calls. But you do need to learn a bit about the internals of Jira and how to code.…
-
I'd start at https://botronsoft.atlassian.net/wiki/spaces/CMJ/overview We're a bit stuck helping here, as you have not told us what you mean by "migrate"
-
Looks to me like someone has gone a bit happy with adding language Apps and grabbed an English variant one and added it alongside the existing built-in one. By "variant", I mean a language pack that is probably still mostly English, but with some stuff renamed for some reason. I've done this before, when an HR department…
-
Jira does not store the date a label is created, so you can't "get" it.
-
Could you explain what geokon is and what it has to do with Jira? Plus the errors you are seeing, plus the expected behaviour?
-
How are you "marking an issue as a duplicate"? Bear in mind that it is something your admins will have configured, Jira has one suggested way to do it, but a lot of people do it differently (better), and we need to know what you are doing before we can help you!
-
add-ons are the old name for apps. But I've just realised the doc you are looking at is wrong - you do not add new apps from "manage", you add them from "find new apps". If you can't find it there, then my best guess is that it is not a Cloud App, so you can't add it to a Cloud system.
-
Did you sign up for the research group?
-
If you don't have the drop-down, either you're looking in the wrong place for it (top right for Server, low on the strip of icons on the left for Cloud), or you do not have admin rights.
-
When you send an email "to Jira", you are not really sending it there directly. You are sending an email to an address which is a post-box. The networks take your mail and deliver it to the box, and then Jira empties the box later. It's a lot like the postal system I have at home. Someone sends me a letter (mostly bills,…
-
What user directory are you using? Is it Atlassian accounts, Google or Identity Manager?