Comments
-
>I am trying to do this on a separate db... Good, that means you haven't done any damage to your existing system. You can simply throw that database away, as it's been made useless by your deletes. Project import imports a single project from a full backup.
-
I think the add-on providing sub-task templates is not compatible with 7.4. You'll need to contact the vendor for an updated version.
-
No, the REST API is simply a service that you call. You're using an https POST to connect. How you're doing that or where from is utterly irrelevant. I suspect you're simply posting data in the wrong format.
-
Software and Service Desk are applications for JIRA, not separate entities. They both run on top of JIRA Core. There's no "integration" to be done, as they're all in the same system. You've got Software installed already, so all you do is add Service Desk and give it a licence - it's under "manage applications" in your…
-
Could you explain what you mean by "checked for "Change log" option" and what you expect from a "Change log"?
-
Not off-the-shelf. JIRA Service Desk assumes that most requests won't end up with development, so the closest you get is the option for an Agent to click "create linked issue in development project" (The Request and the dev issue then move independently of each other with the agent expected to update the customer as…
-
>At the moment I am trying to delete the internal data from the db-tables No. That is going to be a disaster. Please restore the backup you took before you started doing that and change your approach to one that won't trash your systems. Set up a new project on the target system, configure it the way you need it and make…
-
Set up an issue security scheme and then set a security level that says "only group ABC can see these" on the 50 issues you need to hide.
-
That's a broken filter, not gadget. You'll need to get the owner of the dashboard to edit it, check which filter it uses and then find the owner of that filter and get them to correc it.
-
Start at https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html However, much as I'm usually an Atlassian fan, I have to say I really cannot recommend doing this. Cloud works fine if you're starting out with no data, or have a small data set you are happy to manually configure. But…
-
1) what are some of the precautions that we need to take(permissions) so that entire world is not seeing our site Don't enable anonymous access 2) No. If someone can read a page, they can download/copy/screenshot/capture it. This is not a Confluence thing, it's the way computers work - to show you something, your computer…
-
I'd reach out to an Atlassian Solution Partner - see https://www.atlassian.com/partners/search?page=1 I am going to declare an interest - I work for one, and yes, we do cover New Amsterdam, but I don't want to be seen to be advertising! There are other Partners on that page who may suit you better than us, for varying…
-
Not in the Core of JIRA - it's still an issue tracker. But for financials if you're happy with add-ons, give Tempo timesheets + Tempo Folio a go.
-
Your log will tell you why the server is not running. With the one exception that if you performed a hard kill on the process, it can't log that. My advice remains the same. Read your log for the actual error that caused it to stop.
-
I'm not quite sure what you're asking now. JIRA Core provides you with issue tracking - workflows, issues, projects, fields and all the ancilliary stuff you need like reports, users etc. Software adds Scrum and Kanban boards. As I said, you did not put anything in your question that suggested you would really need them,…
-
Start with JIRA Core. Software gives you Scrum and Kanban boards. Service Desk gives you, well, a Service Desk interface for handling support requests. From what you've said, Core is probably enough. If it's not, then try it, and add Software as a trial if you think you might need boards (when the trial lapses, the boards…
-
I'm afraid "Application not accessible" does not mean a lot - what is the context? What's the rest of the error? Where does it happen ("when we access the application" tells us nothing about what you're doing) - login? Visting before login? After login? When you try to use certain functions? "java.net.UnknownHostException:…
-
If an issue is not in a sprint, you can't include it in the metrics for that sprint. If you want to "get the metrics for the work done", you need to put it in the sprint, or report on it separately.
-
Grant "anonymous" access to the project (add "group: anyone") to the "browse project" permission. It's the only way to expose JIRA issues to someone without a login. It does, of course, expose it to anyone who can reach your JIRA system.
-
It's not "JIRA blocking", more that REST is usually implemented only over http/https, as file:// is not particularly useful for REST calls, and you'd have to write a whole other interface layer to expose it, rather than just go with the existing http(s) that comes automatically when running a web-service.
-
Also, can you give us an idea of what "stop working" means? Can't log in? Can't create new data? A blan screen or error message when you visit the url?
-
Indeed. When you want all three, I have a slight preference for installing JIRA Software and then adding Service Desk later via "application management", but you could in theory do JIRA-SD first, or just Core and then add the other two. It's all one server. Software and SD layer themselves over the core functions in, well,…
-
You need to do what it says - talk to your administrators. They can disable users to make space and/or get a licence for the next tier up.
-
An evaluation licence should let you raise one, and you can then explain what you're doing!
-
From memory, 2.3 and 2.4 had serious licencing issues, and are not legally distributable. In your case, as you have 2.4.5, installed at the time, in good faith, I suspect Atlassian might give you a copy. You should ask over at https://support.atlassian.com
-
I suspect they went away because you cleared more than the caches. That will not have affected your data though, and you should be able to go back to the "find new add-ons" to re-install the missing ones.
-
The issue navigator does not filter issues by anything other than the filter you give it. If you say "project = x", it will list all issues in X, irrespective of sprint or backlog. I'm not sure you are looking at the issue navigator.
-
Older versions will happily do that, given the right information in the home directory (if it's off-the-shelf, you're probably fine!) but I've not tested it from 7.0 - I've only ever jumped to 7 by running the installer against 6.x
-
Atlassian has 14ish products, of which the main ones are JIRA, 2 JIRA Applications, Confluence and Bitbucket. All of these separate products are available in three flavours: * Cloud * Server * Data Centre So, from what you've said, you are looking at *three* server products, leading to *two* services running - JIRA Core…
-
A bulk edit will pull up everything in the filter you've used. Go to the issue search and try typing just "project = X"