Comments
-
They should appear as soon as they have been created. Unless * Someone has turned off the panel in the system settings * You've got something deliberately hiding the panel * You have a problem with indexing The third one should show in the logs, the other two, I'm afraid you need to go over your addon settings and check…
-
Try the integrity checker first - that has some functions that can fix workflow states. Under Admin -> Troubleshooting (it does other checks, does no harm to run them all)
-
Er, no. If it is evaluation, it will be read only. If it is a bought licence that expires, it will continue to work. Unless Atlassian have suddenly changed their licence terms without warning?
-
Depends. If it's OnDemand, you'll lose all usage. If it's download, it will continue to work absolutely fine as before. You lose support and you can't upgrade past the last released version, but it'll work fine.
-
You've misunderstood what JIRA is. JIRA is a web application, not a site. Apache only serves up web sites, it does not run applications like this. You need to install and run Jira, then you use Apache to proxy to it as part of your web site. You've got most of the proxy stuff right, but you've not installed JIRA at all…
-
You can turn it off in the "add on management" section. I can't remember the add-on and module you need to disable, but it's there somewhere (check with your users too - when I did it, there was a lot of negative feedback and it was quickly re-enabled)
-
It's not clear what you are talking about here. Could you explain what you mean by "reference / link when we attach files to an issue"?
-
Not telling us what the errors are does not help either. What are they?
-
I'd check the log file for errors to see if that can tell you anything, but the main thing to do is probably contact the addon authors.
-
Part of the workflow, yes.
-
You can't. Your JIRA is way too old. Or, rather, a brief walk-through is: * Upgrade JIRA to 4.4 * Upgrade JIRA to 5.2 * Upgrade JIRA to 6.4+ * Use the UPM to install the plugin from the marketplace
-
Raise it with support - the more they're bombarded, the more likely they are to deal with it
-
Your screen shot is the display of an already-installed add-on. You're looking in the wrong place for install add-on, you should be at the top of the "manage add-ons" page, which has the install link at the top right. But you're also on Cloud according to your labels, so you won't have it - you can only add Cloud or the…
-
I'm more used to seeing the server name rather than IP address, but I've never put a port in there.
-
Confluence has a more simple licence system than JIRA 7, it's the old style. A Confluence licence for 500 users means that you can have up to 500 "active" users (active meaning "they can log in and do stuff"). When you add add-ons, such as Confluence Questions, you need to have a licence that matches the Confluence…
-
Use the most appropriate method for your version and ignore the other two.
-
Start with the standard documentation - https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA
-
Ok, I need to clarify something you have said here, just in case! You say "workflow button is disabled in issues page". Do you mean that the button (menu item really) is visible, but grey? Or that it simply is not there? If it is greyed out, then you have a customisation doing something bad. I suspect you mean the second -…
-
Your upgrade has failed, you need to roll back and then check out what went wrong from the logs.
-
Ok, good, because it will fail if it's the wrong type of task. Again, as I asked before, could you tell us where you have added the post-function is on the list of post-functions on the transition? Also, could you have a look at the log?
-
Ok, that's probably going to give you some useful information in the log when you attempt it (something like "parent doesn't exist"). Could you have a look in the log? And tell us where exactly the post-function is used? (Also, confirm that "Testing" is definitely a sub-task type?)
-
In a lot of cases, this won't work. The issue isn't physically created until the end of the create process, and sub-tasks can only be created on issues that exisit. A lot of create-subtask post-functions will fail because of this. Which post-function are you using? (I.e. which plugin?) And where exactly have you used the…
-
If you're using one of the Atlassian supported SSO systems, then J Caldwell is spot on - raise a support call with Atlassian via your Jira "request support" option under admin. I should point out that they don't do telephone support really, they'll only call you if it's going to get a quicker resolution to your issue. If…
-
It's a technical thing. I think of steps as a framework or skeleton to hang everything else on, including the status. If we got rid of steps, then you'd have to have something else to hang the transitions on, and you'd lose the ability to rename or change status on existing steps, and the xml and execution of the code…
-
>i tried the postfunctions which is already available but it doesnot work You could try to fix that. We can't help you though, as "it does not work" tells us nothing. The other option is, as usual, the Script Runner add-on, which has canned scripts that can do some of it, and lets you write the rest yourself.
-
You could disable the internal user if you're not using it, after making sure another account is in the "system admin" group. That would free up the "seat"
-
That's what I said, yes.
-
Three miserable failures to jump from 3.5.17 to 5.something basically, and no successes yet (although I'm about to trial it on a fourth site tomorrow) I should say that we didn't go into a lot of detail about why it failed so I don't know exactly why. The 3.5->4 we had trialled before worked fine each time. The sites are…
-
The only way to be sure is to test it. However, You absolutely must get to 3.5.x first. (I say x because jumping to 4.something does work for 3.5.11, 3.5.13 and 3.5.17, and probably the ones between as well. But I'd strongly recommend .17) It is possible to jump to 5.0 from 3.5. But I don't recommend it. Go through…
-
You could, but the document you're looking at specifically does not have it on the list, so it's not supported, and so I'd very strongly recommend that you do not.