Comments
-
That looks like a web-server error - I suspect your JIRA is behind a proxy web-server that is asking for authentication before it allows access to the JIRA You'll need to talk to your administrators and network people about this.
-
Not really, the point of labels is that users can enter them. If you want to limit them to a fixed list, drop the labels field and add a "multi select" custom field with your pre-defined list of options. You'll also be able to disable/rename/delete those options.
-
Yes, email is an option. For email, you set up Jira to read a mailbox regularly. When email arrives in there, it removes them and converts them into issues (or comments on issues). There's some email handlers built into the core product which are an excellent starting point. However, you mention some fields - the basic…
-
There's quite a lot of ways of creating them. REST is the all-round answer because you can do that from anywhere, but for the best answer for your needs, you need to give us a bit more detail (even if you're uncertain, just describe what you are sure of)
-
As there's another conversation about this, with lots more information over at https://answers.atlassian.com/questions/252904/memory-configurationsI'm closing this as a duplicate.
-
Or "du" to drill into usage. (Specifically, "du --max-depth 1" is really handy) But, as Radu implies, how do you know you're running out of disk space? What do the logs say on a crash? Always read the logs when you've got a problem like this, they'll either tell you a lot, or they'll tell us quite a lot :-)
-
No. Reads in Jira simply aren't logged unless you make some code changes. Reads in Confluence can be, there is a plugin that does it built into the system, but it's disabled by default because the load it imposes can end up crippliing it. Almost all changes are logged in both systems - that is in fact what they are for -…
-
No. Priorities (and resolutions, to a lesser extent) are a massive weakness in Jira because they are global. It's the most popular unresolved problem with Jira (and has been for many years) https://jira.atlassian.com/browse/JRA-3821 - vote on that, and read the comments for some work-arounds that may help.
-
Attend an Atlassian event, there's usually loads going there, or earn lots of points here and get vouchers for the Atlassian store. There's on-line giveaways too (although I'm not sure the Dragonslayer one is around any more) The easiest Atlassian event to find is a local user group. I don't know about other countries, but…
-
Hmm. I haven't tried it with a new installation. Maybe there's something that Jira detects when it first runs that understands the setting, but it doesn't work for an existing Jira because it's already created the tables. Interesting.
-
Jira expects the names of tables to be a certain case. So the simple answer is that you should not change the names of the tables. If you really must make this change, then you'll need to rewrite the parts of Jira's core that talk to the database.
-
You are looking in the right place - the JRA project contains all the public known issues that Atlassian are aware of. The release notes for a version are essentially the list of things fixed or changed in that release. The list of "known issues" is simple - look at the JRA project for "affects version X" for things…
-
I've just got the same result. I think you've cracked it!I can't see a simple workaround on that at the moment, looks like a bug to me.
-
That error usually happens when there's an incompatible version of JAVA in use. In this case, you look like you are running the right versions, but you do need to check the process - when it's starting and failing, can you use a "ps -ef" to show that it's definitely running /usr/lib/jvm/java1.8/bin/java and not a left over…
-
Arg. This is the same question you asked the other day. https://answers.atlassian.com/questions/133316/write-on-mysql-jira-db
-
You probably want to raise this as a suggestion with Atlassian, over at https://jira.atlassian.com
-
Natively, you don't - numbered headings aren't particularly pretty or useful on web-based docs, so Confluence doesn't have them built in. They do work better on paper and a lot of people print, so you can probably guess that there's an add-on for them. There may be others, but the one I've used most is…
-
To get a read-only user Do NOT use jira-users group anywhere other than the global permissions. This group should be used to say "person can log in" and should not grant permission to do anything else, unless it really is a completely open global option. You don't have to use Jira-users group for this, you can use others,…
-
Yes, it's well hidden. You can probably guess that I had a bookmark!
-
This is old, but the answer is still valid - "no, but there are workarounds". Atlassian have said they won't fix it too - https://jira.atlassian.com/browse/JRA-5865 http://forums.atlassian.com/thread.jspa?messageID=257250857
-
Duplicate of https://answers.atlassian.com/questions/151508/how-to-revert-bulk-move-changes (which has a bounty and more detail)
-
I thought it might be that, but there's been several similar ones recently that don't refer to Atlassian and then go on to be unrelated, so I pasted a stock answer to prompt a confirmation. Whilst I understand the easy option is the file-at-root, and I do understand why it's being done, I don't think it should be the only…
-
Could you explain what this has to do with Atlassian applications?
-
Plain vanilla Jira should be ok for that :-) I'd look at the stuff the system field versions can do for you on the releases side though.
-
It's worth a try - depends on what sort of "non Agile" you're going to try. Jira's workflow and field stuff is quite powerful and most of it isn't hooked into the Agile stuff. Even the "fix version" which does a lot in Agile still has quite a lot of functionality without the Agile plugin. So I'd give it a shot and see how…
-
You could start by simply ignoring Agile in Jira. You don't have to enable it for every project, so you could pull out the non-Agile ones quite easily. Then just work inside Jira as it was built before Agile was added.
-
Comments is not a field, it's an optional place to enter a comment about what the user is doing. You can remove it by removing the user's ability to comment on issues, but generally, don't bother, it's far too useful. The other fields are far more simple - for each transition, look at the "transition screen" it uses. You…
-
Nope, not going to happen. The Agile Add-on does not work on JIRA 7+ It is entirely replaced by the JIRA Software application. If you're running JIRA Software, you have all the Agile functionality. If you're running JIRA Core, then look under admin -> manage applications and you can add it there.
-
No, the best you can normally do is go to the next tier up for a year, or ones that co-terminate with your existing licence. You could install an evaluation licence though, but maintaining that would (rightly) be a pain. If you're making config mistakes that push you over the limit, then you need to be looking at your…
-
The full addon approach is at https://developer.atlassian.com/confdev/confluence-plugin-guide/confluence-plugin-module-types/event-listener-module/writing-an-event-listener-plugin-module But if you're happy installing the script-runner, you can write listeners in there as well.