Comments
-
That's usually fixed with https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html
-
What's a "genomic workflow"?
-
Ok, that suggests the link is in use somewhere. What is it linking to? (In general, not the actual link - another Atlassian application that your JSD might be using for some reason?)
-
From memory, have a look for RCurl - that enables R to issue http calls and grab the data returned. With that, R should be able to call JIRA's REST APIs to pull data from JIRA (you'll need to find a JSON library for R as well, that's where my memory fails me)
-
You'll need to start at the beginning. Could you explain what you mean by * Export template * Export format * Project case Then you'll need to explain what your migration to Cloud is expected to do. Most server to Cloud migrations involve a backup and restore, which is not configurable, you need to start with a standard…
-
What error do you get? Or what's the behaviour if there is no error?
-
It does to me too, but I think we need more detail on the use-case. I'd class this as a "definite maybe" at the moment ;-)
-
Broadly, I know most of it is possible, as one of my squad did it a while ago (specifically to store project-level data for doing calculations in scripted fields later). No idea how, as I've not tried it. But that was a very specific case, and this use-case is too fuzzy to be able to say if that might work for them.
-
Yes, you need JIRA offline to perform the upgrade. I can't emphasise enough that the routine should be * Shut it down * Backup the database * Backup the home directory (although you can skip the attachments as they won't be touched by the upgrade) * Backup the installation directory * Run the installer and tell it to…
-
Confluence is a separate system, so you can ignore that.
-
Groups are a function of the user directory, and hence they are global things, not space things. But the permissions and restrictions work with individuals or any groups, so you can still use them in there.
-
Yes, I said unusual characters as we think there are some others, but so far, we've only run into it with emojis. The one I first encountered was highly appropriate - 💩
-
Your users are sending you emails with certain emojis or unusual characters embedded in them. JIRA running on MySQL does not yet support these, it can't safely write them to the database, so it fails. You either need to get them to stop sending emails like that, move to PostGresql or Oracle, or accept it until a fixed…
-
Only by using injected javascript (which tends to be unreliable). The behaviours module in ScriptRunner can do it reliably, and I think some other add-ons can do it too (not tried others, I don't need to)
-
Yes, I can see it's a bit of a pain. Without knowing what type of field it is now, I can't really give much guidance - you might be able to change the field template, or the searcher, or you might need to migrate to another field.
-
That's not a contradiction. The price is 2$ per user. The number is unlimited. If you have 1 user, it's 2$ a month, 2 users is $4, 10 users for $20, 20 users for $40, 4,096 users for $8,192, and so-on.
-
Glad it'll be minimal complexity to remove this downgrade. And very good that it won't affect your upgrades or support (hacking code does)
-
Ah, you'd need admin rights to get into the list of custom fields to see the type as well, that explains why you didn't get it in your screenshot.
-
You'll need to code to do that. Do you have any scripting add-ons installed,or do you prefer to write your own add-on?
-
Ah, different version of JIRA, the field type should be underneath it. If it's still not there, then can you try the "edit" link for the field and see what that says? And then "configure" if there is the option to do that (some fields don't have configure)
-
I very much doubt your custom priority field is id 10000 - you need to re-read the doc and use the right one. The code you've copied and pasted also assumes the field is a string, which it may not be. Also try debug code - add <p>My debug</p> just above the "if" lilne, and make sure that appears in the email - if it does…
-
First, have you considered JIRA Service Desk? Which has all of that? Second, if you're not going with JSD, have a look at https://marketplace.atlassian.com/search?product=jira&query=sla
-
Could you increase the frequency of the subscription, so that you get the mails quite a lot - do any of them arrive at all? Also, on the subscription, make sure you have the "send even if there are 0 issues" to ensure it always tries to send.
-
Moving an issue to another project is a very poor process, and not a trivial thing to do in JIRA, as the config has to be checked for compatibility and the user possibly asked many questions. Moving it to another sprint is also not a good idea, as sprints should be determined by the scrum team, not inflicted on them by…
-
There's not enough information here to be able to help you. You've got JIRA, and a couple of laptops, but you don't explain how you're using them or what for.
-
Hard to say without ther rest of the error - "null pointer exception" is Java's generic "it went wrong" error, and there's usually more information later in the report.
-
Edit the workflow for Task 1, and look at the "conditions" on the transition into "done". You will want to add the "sub task blocking" condition to it (you don't need to worry about the sub-task workflow having this condition, or if there are no sub-tasks on a parent - if there are no sub-tasks, it won't block anything)
-
Project import only brings in the issues. You will need to set up all the schemes and project config manually.
-
Yes, it won't cause a problem because if Synchrony is broken, all Confluence does is disallow edits with it (with a pretty useless error message for the user though). After the upgrade, just check the "use collaborative editing" flag is "off", and it'll use the old editor.
-
I suspect the workflow for the issue has the "do not allow edit on this issue" property set on the "closed" status. You will need to transition the issue out of "closed", or change the workflow to remove the property.