Comments
-
I assume you're going to install Service Desk into the existing Software server? If you do that, you'll be working in the same place and hence have a lot of "integration" already. Even if that's not the case, there is a question: What do you mean by "integrate"? What do you expect to get from it?
-
There's lots of ways to do it, but I'd strongly recommend using add-ons.
-
Not without code - the clone process really does clone them, sprint and all. To avoid that, you need a different clone process. The marketplace might have a couple of options, but you may have to write it for yourself.
-
It's in the system information page. But you shouldn't be reading the database, it's really not the best way to do anything other than running the application.
-
Ah, sorry, yes. Login as an admin and go to Admin -> Backup and Restore and select the "restore" option. It should ask you for the file to import and warn you that you're about to delete everything
-
A simple clean way of "resetting" a JIRA is to re-import the startupdatabase.xml file that it creates in the import directory on start-up. It is a hard reset though, you won't get to keep anything at all. Projects, users, schemes - all gone.
-
It sounds like you are not using the right text renderer for the fields. Could you check the field configuration for the project/issue-type and the description field? Make sure it is not "plain text"
-
You need to reverse the operator. Computers tend to think of human date/time as "a count of time fragments (usually milliseconds) since a base date". So "half an hour ago" is "now - 30 minutes" Your createdDate > -30m is thinking backwards, using "now" as a zero point, but that's wrong, because the zero point is (usually)…
-
You'll need to contact https://support.atlassian.com if this is a Cloud system. (If it's Server, see https://confluence.atlassian.com/jira064/retrieving-the-jira-administrator-720415928.html )
-
No, you have not read the docs, and you're inventing nonsense urls now. Please use the urls that are documented. The put/get/delete commands are commands, not something you randomly insert in a url. And, as we've already discussed, your first url is the wrong url for accessing components.
-
* The PUT is required to tell JIRA that you are posting data over. * Try a GET http://yourserver/rest/api/2/project/<project id>/components - that should list them all out for that project * No, you need to use the component calls.
-
Your application should use the Component REST API to update/delete the components.
-
No, the Atlassian backups are there for them to do recovery, and are taken at slightly variable times (because they're backing up thousands of Cloud systems). They're not intended for end users to use. You can ask, and they might do it, but don't expect them to do it regularly. If you need backups, use the ones provided by…
-
The backups that you, as an end-user, can get to are different. They are created when you ask for them, with a maximum frequency of one every two days. You just need to click backup and download, and Quentin's link shows you how to automate it. But the answer to the question you've asked is "you can't". The best you can do…
-
The only way to do it for Requests is to have a request type that is mapped to a different issue type. (In plain non-service-desk JIRA email handlers, you can set the issue type in the handler. JSD asks you to set the request type which is then mapped to an issue type)
-
The only way to do it is have the emails create a different issue type. I'm afraid your last sentence describes how it works - JIRA doesn't care how things are raised, just what the issue type is.
-
Yes, you can add lots of components. Might get a bit confusing for the users, but I've seen projects with >1000
-
At a guess, I'd say that while they have system-admin rights, they don't have project-admin rights on the "missing" projects. (It's important to understand that system-admin does not mean "can do everything" as that's a very badly broken security model, and hence, not implemented by Atlassian). Check the permission schemes…
-
I suspect the Script Runner add-on First, check that the add-on is a version that is valid for version 7 - this error can happen when you're using an incompatible version (because you only upgraded JIRA and not the Script Runner). Ideally, go for the latest valid version. Second, have a look at all your scripted fields.…
-
So you can look at a Jira issue and see an answer to "what files did we commit to fix this". It is in the description of the plugin...
-
Yes. See https://confluence.atlassian.com/display/JIRA/Jelly+Escalation
-
Yes, your filters can use absolute dates instead of relative ones.
-
I'm afraid I don't know of anything like that - you'll need to code something. Or just create a dashboard with 5 filters in separate gadgets. Or select something more useful than just "number filter returns" like issue type, project, assignee etc.
-
You'll need to tell us what the errors are and maybe what has changed since you last logged in.
-
LMGTFY - http://confluence.atlassian.com/display/JIRA/Listeners
-
Are there sub-tasks in the project's "issue type scheme"? And do you have "create issue" rights in the project?
-
JIRA Core doesn't have "boards", and there's no easy way to get close to that view in Core. But there's nothing to stop your Operations team using JIRA Software's boards. JIRA Core supports plenty of addons, and more every day as add-on vendors update their software so that it is compatible with JIRA 7. Note that the list…
-
Ok, that's being worked out as the page is rendered as part of the Toolkit add-on that provides the tab. You will need to duplicate the logic behind the field in your code.
-
How are you creating the "last execution date" information? It doesn't sound like a field to me (which would explain why you aren't being offered it in the post-function settings), so we'll need to know what it really is to begin with. First quick check - do you have "last execution date" as a field in the list of custom…
-
Not a clue. You haven't told us what Atlassian system you are having problems with, or how you have configured user authentication in it (Crowd, internal, LDAP etc)