Comments
-
You don't want to bother. Cleaning the caches is not going to help you with inserting data in the database, because you would need to lock out all the users, clean the caches, run your SQL, prompt it to rebuild the caches, prompt it to re-index any issues affected and then let your users back in. You'll also need to write…
-
You can use any language that can talk to Jira via REST (or SOAP) if you want to do things externally. They should support https fine (the stuff I've written for it certainly does)
-
Niels is absolutely correct, you can NOT insert data directly into the database. Jira caches data. both on disk and in memory, and that can overwrite anything you try to push into the database. If you have no other option than a database change, then this caching means that you cannot do it while Jira is running. There's…
-
Raise it with Atlassian OnDemand support...
-
Not without tinkering with the templates I'm afraid - it's general guidance text
-
There's several places you could be talking about, is there a specific one? In most cases though, the answer would be to change either a language file or a template file in the core
-
Yes, but it's a pain, you're better off using the API. (Join project_role_actor to cwd_user, but you'll need some more joins to work out what exactly to read)
-
And there's an inherent problem with the idea. Yes, "highlight what has changed", that's fine, but you need to think about "since when". And that's a horrid can of worms which will give you a headache.
-
All xxx.atlassian.net urls are for Cloud installations, so that's an easy one to confirm Your server licences have nothing to do with the Cloud ones, so that will not be the problem either. You can't use server licences on Cloud at all. If the Cloud page is throwing that error, there's one of two things - you've either let…
-
I'm afraid you need to explain that in more detail. You can't access something Atlassian related, probably a JIRA installation, but you have not told us what you can't access, where it is, what the error is or what you're trying to do.
-
See https://jira.atlassian.com
-
Matt beat me to it. The field configurations and screens are totally separate things. You have two field configurations, but when you use the link to the screens, you are adding/removing the fields on the same screens.
-
Not without code, and you'll need to define some rules more carefully. "In the same group as other user" is essentially useless. In most Jira installations, that rule works out as "everybody" because the default access model is "everyone who can log in is in jira-users, so everyone IS in the same group as me" What you need…
-
No, the upgrades currently need to be started manually, or by the installer. The system cannot upgrade itself while it is running.
-
Ah! I understand now. Sorry!Could you check something else for us? Go into the "field configuration" for the project and issue type. Look for the field "original estimate". Is it listed at all? Then:If it is listed, can you check if it is required or not?If it is NOT listed, could you find the field called "time tracking"…
-
I'm sorry, you want it mandatory, but not? I don't understand this.
-
Ok, so what is the actual problem? It sounds like you have made "original estimate" mandatory in the field configuration, but I don't understand " which is placed an estimated time but querere Save the message that appears Required field."And again, what happens if you disable/remove the jira suite utilities addon?
-
We can't read your support requests, and you have not told us what addon it is. But. What happens if you remove the addon? Does it work then?
-
Did you drop all the old tables before importing?
-
What does the application log file say is wrong? (In confluence-home/log)
-
Yes and no. For "upated", use a REST search. You haven't defined what you mean by "updated", but you can search for pretty much anything you want. For deleted issues - no. Deleted issues have been deleted. You can't search for stuff that's not there.
-
That's a question about your processes, not one we can really answer. Generally, assuming a pretty standard and common way of doing things, no, you'd create a new issue, but that might not be the way your organisation really wants to work. If it were me, I'd only re-open issues that have goine into a production system if…
-
I'm sorry, I don't understand that.
-
You can create groups in Admin -> User management -> Groups. Then put people in them.The best way to use them in projects is to go to "users/roles" in the project, where you'll find you can add individuals or groups into project roles (when you use a group in a role, it's basically just saying "everyone in this group is in…
-
Correct. If you place a Project in a Country grouping (you could use project categories if you have no other use for them), then yes, by implication, users in that Project would belong to that country.You could use groups to do this, yes, users can be put in many groups as required. You might find it easier to use roles…
-
I think I'd be tempted to group your projects by country that they're working in. That way, you can group your users and clients appropriately, without losing the ability to go across borders when it becomes needed. For your "subincidencia", yes, JIRA supports "sub tasks"
-
The standard email handlers in Jira only do "create or comment", there's no parsing of the email beyond looking for an existing issue to comment on. You need to find/write a more advanced handler that will read the body, extract what you think you need and import it. Personally, I rarely bother writing anything at this…
-
Yes, you could do some updates if the API supported it. I've not looked at doing that in the Service Desk API though, so I don't know enough about it. If you can't find an update, then my guess is they haven't enabled it (yet) Do NOT even think about doing this in the database. Messing with a JIRA database is a nightmare…
-
The REST interface respects what you have set up in the screens, so no, you're going to have to think about this differently. I suspect the only way you'll get to do this would be to move the "edit" of this field into the workflow (have transitions that go back to the same status, with a screen with your field on it), so…
-
Drag it to another column on a board, or go to the full issue view and click a transition button, or use the cog icons in a report (issue navigator etc).