Comments
-
Check the startup scripts for Jira, it sounds like JAVA_HOME may be being set in there. You might also need to set it for the user account that runs Jira, rather than your own, or even amend the system default. (I can't be sure where the scripts are becasue I don't know how you've installed it. Look for a "bin" directory…
-
It's not my code. And what code there is is limited by html and programming languages. I'm not suggesting you don't work with other countries, Confluence has a huge market across many countries, including significant and rapidly growing ones in areas that don't use roman-like characters at all, and it works well in all of…
-
"Special characters" is not peculiar to Atlassian, they're defined by the whole computing industry, and are a bit of a hangover from the times when every bit counted. When you've only got a baseline of 127 characters to work with, then once you've dealt with control characters, punctuation, numbers and two cases for the…
-
Whatever "export to txt" you are using is not generating the correct language characters. You'll need to debug this "export"
-
The best way to do it is forget the download and use the "admin -> add-ons -> find new addons" to find it and add it. This is the approved route (and it protects you from installing invalid versions of add-ons) If you want to do it by upload, then there's an "upload add-on" link in the manage add-ons section Of course,…
-
The pages you're reading on "base url" mostly have "this does not apply to Cloud" in a box at the top. You can't change the Cloud base url directly, you have to buy a new Cloud instance, export the current one, and import it into the new one.
-
There's no need to change the base-url, it's fixed and correct for Cloud instances. If Confluence is jumping straight to "create a space", it suggests that there are no spaces yet - I would try creating one, making sure you give yourself at least the permission to view the space. Then you should get full access to all…
-
Duplicate of Errata - in setup of tomcat issues for confluence
-
Ok, I'm not sure what "within 8" means? 8 over/under what? Of the 8 that are mismatched though, is there a pattern to them? Same issue type for example?
-
Do you have 98 sub-tasks in the filter?
-
Yup. You need to make the field optional in the field configuration. I'm only commented to clarify that Nancy is spot on because Jira's field configurations are very black and white - a field is either mandatory or optional, throughout it's lifecycle. Screens, other fields, status, where field is used - all utterly…
-
Admin -> manage add-ons
-
Good catch, I suspect that add-on was injecting something that was cached and broken.
-
That's actually the browser, not JIRA. Could you try a different browser (and maybe "safe mode" in your current one) to confirm this?
-
The drafts are kept in the database. If you accidentally destroy your Confluence installation, create a new one (including a new "home" directory), and point it at your old database, you'll find your drafts are there...
-
I think Thomas-S is right here - you're at a point where you could explain in great detail what you think you need to do, and hope one of us has the time and energy to read it all and try to work out an answer. Or try it for yourself (and ask again if you get stuck)
-
It's all covered at https://studio.plugins.atlassian.com/wiki/display/JEMH/JEMH+Home (and the answer to 3 is "yes")
-
Hmm. Well, the built-in email handlers only do create and comment. To work with fields, you do need something more advanced, and that's where we reach for JEMH - that can be configured to draw field information out of emails. I don't think there's any question that if you're going to do this with email, then you need that…
-
It depends on what you want to do, how complex it is, and whether you've got the resources to write the listeners. You can do this "integration" without any code really, by setting up a simple loop where one Jira uses the standard notifications to include the send of mail to the other Jira, which is then configured to use…
-
The Jira command line "plugin" actually lives outside Jira on a client machine. You don't install it in Jira. If you write your own command line, you will need to do it the same way - write something that talks to Jira via REST (the Jira command line plugin uses a mix of REST and SOAP, although it may have moved to nothing…
-
Priority is a global field with a single list (there's a very old request for project schemes, but it's still open with no sign of Atlassian ever dealing with it properly), so you're pretty much stuck. Your options are * Botch it with javascript (don't, it's hard, flaky and a pain to get right, let alone maintain. I only…
-
You could rename "approved" by editing the workflow or going to Admin -> Issues -> Status and altering it there. This would affect all workflows that have "approved" in them though. If you want a new status, just add it to the workflow, move the transitions in and out of the old "approved" to the new status and delete the…
-
You have not given us much to work with - we probably need you to explain more about what you are doing and expecting. However, I am going to guess that you have signed up for Confluence Cloud trial. New Cloud services take a few minutes to become available. I'd suggest making and drinking a cup of tea and then trying the…
-
Basically, no, you need add-ons or code change to enable SSO variants. Ideally, stick to well maintained and well known add-ons such as the one Bruno mentions.
-
Step back from that, forget GH for now, and define a workflow that encompasses it all. When you're happy the workflow covers all your steps, then go back into GH to see how it overlays it all. If your workflow looks too big, then consider splitting it and having separate projects or issue types and getting your people to…
-
Boards are more graphical displays of your issues. Imagine each issue is a post-it note, stuck on a board in front of your team (that is exactly where the phrase comes from - a board covered in cards or notes). The board has columns representing the status of the issues. You use them when you need them. They're immensely…
-
That's not what Service Desk customers are for. A customer is someone who raises requests, not someone who monitors time logged or spent - it's not important to them. To allow time reporting, you'll need to make them JIRA users.
-
Depends on where you are hosting your Atlassian stuff. * OnDemand - go to your OnDemand account and buy more * Other hosting company - ask them * Your own installation - go to your my.atlassian account, buy more licences, paste the new key into the licence page in the applications admin->licence section
-
But that's the whole point - each board will need to be modified to fit what you're doing, with different projects and workflows. So a template doesn't have a lot of use.
-
There's no board template functionality in JIRA Agile, no. I'm not sure that this is a bad thing though, as a Kanban board really should be built to fit to what the users need, not just "one size fits all"