Comments
-
Why are you trying to download the .jar? There are three things you might be writing here: * A Connect addon * Something external to JIRA that talks to JIRA over REST * A JIRA addon In the first two cases, the .jar is not needed because you're not coding directly in JIRA and you need to use the REST API to get to the data…
-
You can't add a regex, you need to swap to a mail handler that does have the regex functionality. Turn off the existing one and pick another.
-
I mean exactly what I said - you need to write code to do this. You can't do it without writing code because there's nothing to do it yet. I'd have said if there were other ways to do it.
-
If you write code that can create a project and put it into an email handler, then yes. I've not seen anything that will do this, but I can't see any huge obstacles blocking it. (Except that it's a LOT of coding just to enable something you should use sparingly)
-
I'm not quite sure what this means. You say "For some issues it lists only in project" - what do you mean by "lists in project"? Does it come out in a search somewhere? Or a report? Where are you seeing the link to the issue? My guess is a broken index though. If you have a small JIRA and/or can tolerate the down-time,…
-
You can't install plugins into OnDemand. For OnDemand imports, I think you might need to go via CSV or some other route.
-
Internet Explorer - the world's favourite browser (for downloading the proper browser you actually want to use...)
-
I think it's still a case of watching the release pages and https://jira.atlassian.com/browse/JRA-29448 for updates.
-
Atlassian tend to release things "when it's ready", they rarely commit to specific dates, because there's no way to tell if something is ready until it's tested properly, and once it's been tested properly, then it's kind of ready to announce almost immediately. I imagine they will support IE10, but I don't think you'll…
-
It's possible that can have an effect. Ideally, though, you're using some form of DNS, so that <myserver.ourdomain> always resolves to the current ip address of the server. The use of DNS means that you can mostly ignore ip changes as long as the JIRA base url does not change.
-
Actually, not painful at all, once you know where to look (which is, of course, less than obvious) Stop JIRA, clone your database to the new location, then go to <JIRA home> and find the text file dbconfig.xml. Edit the location in there in a text editor, and restart JIRA.
-
This is a networking issue, not JIRA (as you can get to JIRA internally, you know it's working). You need to change your network so that it exposes your JIRA to the internet
-
It's for threading replies. If you don't use (and don't plan to use) creating comments via email, then you can safely remove the records. If you do use them, then it's actually still well worth thinking about killing them off. There's a load of information at https://jira.atlassian.com/browse/JRA-9979 which will help you…
-
Yes. See https://confluence.atlassian.com/jira/migrating-from-jira-cloud-to-jira-server-299569790.html
-
You could write it as an addon, but I'd use the script-runner plugin - saves you the hassle of coding a whole addon.
-
Write a post-function to do it. But you'll still have to present the field to your users to fill in on issue create. Your other option is to bodge some javascript into the 4 or 5 places where you're asked for a summary in an issue. You'll still need the summary on-screen, but you can hide it in the html.
-
You need to be a system admin to do that, not just the site admin. Only Atlassian Cloud support have system admin. I think they'll enable it for you if you raise a support request at https://support.atlassian.com (although I'm not 100% sure of that, given that the add-on is disabled by default because it can cause…
-
You could try something with javascript, but it won't be effective - the field will be visible in all sorts of places, including the raw HTML of the issue view. The standard workaround recommended is the Quisapps Field Security addon. This can hide fields quite effectively (although users will still know that the field is…
-
Directly, this would be a bad idea * Confluence would not be a ware of any changes made outside its interface, * the file naming convention you'd have to stick is not in the slightest bit user friendly * Confluence can cache files, so people loading something you've updated in the UI might not get what you expect It is, of…
-
When it's got a cost next to it, you can usually assume it means "month". $20 per month
-
You can't do it. The "create" transition only has one end-point. You can, of course, do it differently by issue type (different workflow = different start point). The other option is to use an add-on like Script Runner that can perform an automatic transition after create, and pushes the issue onwards through the workflow.…
-
Not really. The reason the gadgets ask for a project is that there is no "associated project" for users. A user can have one or many permissions in a project, none of which are a definite "this is the main project for the user". Jira has no way of knowing what your potentially completely random criteria for "associated…
-
The use of leading 0s in the numbers also made me thing the question was about database ids because Jira Key numbers do NOT have leading 0s.To add more support to what Andy has said, there's really no problem here - you can't have the same numbers in the new project because that causes data issues (not least the problem…
-
One immediate thought - a lot of OS's say "can't find file", when they should say: * file is not there (you've checked that) * file has strange characters in the name that confuse it, so it's not there (unlikely, but I had to mention it. Copy the path and file name and try an ls with the pasted string) * the account trying…
-
You've answered your own question - filter for All Open Issues, and stick it into a "filter statistics" gadget with the stats field = Project.
-
No. Assignee can't be more than ONE person, let alone two. It's a single select, and it's a single person because as soon as there's two, in real life, you don't know who is responsible and ownership goes wrong. Have a read through…
-
You need to look at the project's administration screen. Not the list of projects, but admin for that one project. Not even sure why you looked under user admin.
-
Check the "maintain watchers" permission in the project's permission scheme.
-
Nope, and you might want to try asking in a visual composer support forum, not in a questions site for Atlassian products. Or, explain how this actually relates to an Atlassian thing.
-
There doesn't seem to be a question here. You've given us some screenshots and suggested some sort of network failure, but not really described the problem. If the problem is a network issue, then you need to debug your networks. If the problem is a Jira issue, then you need to describe what it is, and look at your log…