Comments
-
No. If you have two JIRA installations, you must have two separate datasets for them, and they will be separate systems.
-
No. There is a "clone and move" plugin, but it's not available for OnDemand, and there's no work-around I know of.
-
The only update I've got to that answer is "SOAP is not an option at all any more, it went away in JIRA 6.4"
-
Ah, I was expecting the standard "can we integrate" without any definition of what the user means by "integrate", but this is unusually clear. Yes, you can do this, but you'll need to do some coding, and put a bit of thought into it. It's worth breaking into two parts which you can think of separately. First, there's "do…
-
Yes, it has them. Do you have a specific question?
-
There's a long-standing problem with JIRA's comments in that they do not have a history - if you edit or delete a comment, it's not tracked, so you can destroy the sensitive information that way. But issue history - no, on Cloud, your only real option is to delete the issue. You can clone it first to preserve the current…
-
T2-M4's cousin? Not sure this is the droid you are looking for.
-
You could use Workflow properties to remove the "browse" permission for the issue. It's going to do horrid things to your reports and usage though.
-
Have a skim of https://www.atlassian.com/cloud/security
-
Your base url is incorrect, it should be the root of where you want JIRA to run, not the landing page. It really should be http://localhost:8080 for the url you have given. If you're getting redirects when it's set correctly, then you've set something else incorrectly. Could you try setting the base url to what I've said,…
-
My guess is you are using JIRA Cloud, where the function is restricted so you will never see the option. It is turned on in Cloud though, so you don't need to worry about enabling it.
-
Ok, that makes sense. You'll need to write either a service (which can run regularly) or a post-function or listener (those can run on issue changes) which can reach out, over SOAP to your other system and pull the data in. These things are written as addons, although you could try to script it in the Script-runner addon…
-
I'm sorry, but repeating the question does not answer the question I have asked. Please explain
-
I'm not quite clear on what you want to do here - are you suggesting implementing a new SOAP interface in JIRA? Or something that runs outside JIRA, listens for incoming SOAP calls and translates them into something JIRA can work with?
-
There's two things to look at on there: * Look at the workflow for the missing transitions - check the conditions on them are not stopping your users * Check the permission scheme for the "transition" permissions
-
It won't do it. The point of the Service Desk is to allow customers a very limited view of their requests. Customers are lightweight accounts and are not expected to have much interaction with anything other than their own requests, and the participant thing is just for a bit more cross-purpose sharing. If your customers…
-
Yes, you could add another step in your workflow for "release to prod" as well
-
Yep. Question?
-
Ugh, no you don't. Think about your users - I need some help, so I go to a help portal. The last thing I want is to have to click through to get to the place where I can ask. Give me the portal, immediately, with as simple an interface as possible. If you insist on breaking the user experience, you could try to wedge some…
-
Ok, then I suspect the tuturial code you have is simply unsuitable for version 4. It looks like a more recent version is targetted. The messages you are getting imply you might have got the class names wrong in your code, there's a reference to "user" in there which could be a huge problem depending on what the code was…
-
Did you remove all the attempts to get this to work from the pom.xml and code? You've mentioned cleaning out various things, but have you returned to the original code that you got from the tutorial originally? And was that code for version 4 of Jira to begin with (A lot of plugin code for v4 won't work with v6 and…
-
I suspect it's your attempts to get the dependencies right while the wrong Jira was in place. Also, that could be down to your code, but that could be down to your coding tool or libraries. I'd be tempted to start clean with a new plugin directory - but change the pom.xml before the first time you run atlas-run/package etc
-
I'm not sure the tutorial's code is valid for Jira 4.4, however, let's solve the second question first, i.e. that you've changed your pom.xml correctly, but the latest version of Jira starts up This is because the kit does something quite simple when you run the build - it looks for a Jira installation in the target…
-
I don't know. My best guess is that your network admins had set up something that was doing the rewrite for Confluence 3.5. The newer version of Confluence may have changed the url formats (noticably after completing actions?) so the old filters can't pick up the rewrites. But I really am guessing. On the 3.5 install in…
-
Confluence only expects to run on one url and uses the "base url" to define it. It sounds like your base url is set to the external url, so Confluence is happily using it to generate the next url to go to after many actions. There is no way to "fix" this inside Confluence, because it's not doing anything wrong. I'm not…
-
Are you really running JIRA 3.13 here? If so, this is a problem I've seen in there that is fixed in JIRA 4.
-
Resolution is a field that JIRA uses to decide if an issue is open or not. If the field has any value set, then the issue is resolved and is excluded from reporting on active issue lists and so-on. If the field is empty, then the issue is unresolved, and JIRA will display "unresolved" to show that. Status shows the user…
-
Go into your Atlassian account and look for the payment options there. If you don't see one that works for you, contact "sales at Atlassian dot com" or raise a request at https://support.atlassian.com
-
Duplicate of https://answers.atlassian.com/questions/46075587
-
Ok, you'll need to write an add-on to enable that display in JIRA.