Comments
-
Most export/import routines will retain the user accounts in some form, so someone who was an admin before should be able to log straight back in as an admin in the imported system. I assume that's not the case here, as you are changing the user directory system during the move? If that is the case, try these two:…
-
There are several flexible reporting tools in the market place. You could write an external one that uses REST to pull data from Jira. Or write your own. See https://developer.atlassian.com/plugins/servlet/mobile#content/view/4227176
-
Depends on how you've installed it, but Linux is a lot cleaner than windows. There's no messing around with services, registries or system settings to get Jira to work - you can simply work backwards through what you did to install it to work out what needs to go. e.g. if you downloaded standalone and installed it under…
-
The usual approach is to map the priorities together, although I know that's a very general comment.As for severity, that's always been "use a custom field". Historically, Jira did have severity as a system field, and it was deliberately removed - the reasons are at…
-
You can't alter the built-in summary without hacking the core code that provides them.
-
Nope, not that I could find.
-
You can't, they need space admin rights to do it.
-
Oh, I'd forgotten that they've dropped older versions. You could bother Atlassian for a copy, but you could just upgrade to 4.4 and then do the move
-
No. You need to upgrade from 3.13 -> 4.4 -> 5.2 -> 6.4 -> 7.x The migration can be done at any point, but as you have a new machine to work with, I would install a clean 3.13 on that, import your data, and then work through the upgrades (obviously, do test runs of that first) You may discover that you can skip the 5.2…
-
I forgot, if you want to persue the listener route, then 1. Have a quick look at the "auto transition listener" in the Jira toolkit 2. Jamie's script runner plugin can make it even more easy
-
The short answer is what you expected - No. I've seen various attempts for people to try to write post-functions that try to change the end point of a transition, and I've yet to see one that works cleanly or safely. I've had to clean up the mess made by a couple of attempts and it's really ugly. The reason is simple - a…
-
Yes. That's the simple answer. All you need to do is change the filter for the Agile board so that it includes both projects. Then you'll see all the issues together and can drag them into the sprint as required.
-
5.x and, when it's released, 6. Although the closer you get to 5.10, the better the integrations get.
-
Same as it is for any other servers. Buy the licence, go to your my.atlassian account where you'll find the licence, enter the server-id from your Jira system, copy the licence key and paste it into the Jira licence box.
-
Scrum boards track an issue through its workflow. The display you've defined is not a Scrum in any way shape or form, it's a basic report. Go to issue search, define a search for the issues you want to display and run the search. Save the filter, then use the options cog to set the column order for the saved filter to the…
-
No. That version of Tomcat should be fine. Look at what has happened. * You had a working Jira. * You changed something. * It stopped working. Running off and blaming random problems in software that don't seem to relate to the errors in your logs probably won't hlpe much. I don't see how upgrading the Tomcat is going to…
-
Well, they can use Apache - most places I've worked put Jira behind Apache for various reasons, and it works fine. We've still got the problem that we really don't know what you've done, or changed, which is clearly the problem. As you've said it worked before, there must be something you've changed that broke it, and…
-
There's still not enough detail to tell from that, but you need to explain what you've done. You imply it was running before - the question is therefore "what did you change" and then "what happens whwen you put it back the way you found it" If I've misunderstood, and you've never had it running, can you explain how you…
-
Yes, the error you are getting is usually to do with the connector settings in that file. But those look fine to me - standard off-the-shelf ones, so it must be something else. What other errors are you getting - could you describe all the symptoms?
-
Check the connector settings in Tomcat. Although if this is an OnDemand installation, I think you need to throw that back to support as you won't have access to that.
-
1. Yes 2. It's not a default, they're written in Java because that was the language of choice and there's no need or even desire to duplicate it in another language. That would be a pain because instead of saying "use this java class to authenticate", you're suddenly having to provide the framework to support an entire…
-
Much as rebranding "Confluence" as "JIRA Wiki" was something I enjoyed discussing with an Atlassian at last year's summit, they are two different applications. As you talk about wiki and have used Confluence labels, I'm going to assume you mean Confluence, and your mention of JIRA isn't really relevant. The best method…
-
https://answers.atlassian.com/questions/252843/how-to-find-the-unmapped-groups-in-jira?page=1#252872
-
Yes.
-
At the last Summit I had a jokey conversation with an Atlassian about re-branding Confluence as "Wiki for JIRA" and doing it as an application It's not though, Confluence is a standalone server product, not an add-on. It integrates well with JIRA, of course, but it is separate. I'd still recommend that you have a look at…
-
Confluence add-ons don't work in JIRA (with a couple of exceptions for very generalised add-on) - they're two different systems doing different things, and have very different APIs Could you tell us which add-on it is, and what you are trying to achieve?
-
Yes. You can write addons that give you both reports and gadgets, and share the code so that you can add a report as a gadget.
-
I can never remember exactly which addons do things when it's the really basic stuff. I always install JSU, the Toolkit and Calendar before I try anything with workflows.
-
There are conditions in plain JIRA for system fields, but the option to check custom fields is provided by add-ons. There are loads that do it, but it would seem you've dropped the one you were using during upgrade. Off the top of my head, try the JIRA Suite Utilities, Misc Workflow Extensions and, well, anything else on…
-
Well, yes, you could revert it, but that won't help you with these user issues. It sounds like your Jira can't connect to LDAP - whatever you do, you need to find and fix that.