Comments
-
What do you mean "database check too long"? It looks fine to me from your log.
-
I think you might want to explain this question a bit more.
-
The usual problem is the network connection between you and the data centres in the US. Other Cloud users do not have any problems with speed. As Stefan says, a good option is to run it yourself - that way you can put your server inside your own networks, and give it all the resources you think it needs. Of course, there's…
-
Partly. Cloud has the REST api, so you can do the "C4C pokes data into JIRA", but C4C will need to support webhooks in JIRA to get data to go the other way.
-
Not really - you're going to need to find or write code that C4C can execute to push data into JIRA over REST, and then some more for JIRA post-functions to do the same in reverse (assuming C4C has a remote API of some sort)
-
Probably, but you do need to define what you mean by "integrate".
-
> This is the most dangerous allowance as someone may be able to go through and mess up a lot of issues for example without having to account for changes Ah, but Jira will track their changes. If someone does make a mess of it, you can look at the the issue history, see who did it and blame them :-)
-
It's definitely better to keep "System Admin" away from "Managers". For your needs, I'd simply define a new role of Manager, edit the permissions to allow move, assign, edit (I'd think twice about "delete" because it really does destroy the issue entirely), and then amend your workflows to alow the role to complete (As…
-
No. If you're importing a group name, it's imported as it is. It's not a local thing, it's using the AD group.
-
I don't know what webappscf even is.
-
Ok, you'll need some code to do that. I'd do it with the behaviours stuff in the Script runner for JIRA, and a script on the post-function that sets a value when the field is left empty by customers.
-
I don't understand the question. You've got an nFeed field (which draws data from an external database). You have a user who logs in and creates an issue. I guess they are seeing the nfeed field but I don't understand what you are trying to do after this point.
-
It depends on your requirements. If they're tied to users, you probably want to do something with your user directories. If they're tied to projects, think about project fields (done by a plugin) or metadata. If they're tied to issues, then your current "log user at the time of issue create/edit" is the right approach.
-
Ok. So how are you planning to store the information that "Alice, the assignee, has a resource manager, Bob, and business leader Charles"?
-
I am sorry that I do not understand this, but your last post makes no sense past the first half of the second sentence. Three managers per user is a really broken way to try to run an organisation, bit it can be understood. Storing that relationship makes sense. I have no idea what the rest of your comment means
-
Actually, that's probably the easiest way to do it. If you are collecting and storing the manager in a user custom field, you simply add the field to the notification scheme and they'll start getting the mail (you can send to people like reporter, assignee, group, etc - look for "custom field" on that list)
-
How are you storing it in Jira?
-
Ok, that's a start, I think you've misunderstood the global permission. In order for a list of potential assignees to show, the person DOING the assigning must have "browse users". This explains what you're seeing now, if I've read your testing correctly. You have this: * jira-developers has the right to "browse users" set…
-
Do you have the right to "browse users", set in the global permissions? (I think it might be set by default, and hence you probably do, but it's worth checking this, just to rule it out)
-
The add-on for JIRA is free. TestRail is not. If you want to use TestRail, you'll have to pay for it. If you do decide to go with it, and you have JIRA, then the add-on will not cost you anythign more to add to JIRA or use.
-
(Oh, and the case with the dodgy typists - I once worked around this "problem" by writing a field that took the non-stattable data and made it stattable - worked brilliantly for a while, then ran into massive performance issues as the data set grew. The chap who worked out what I'd got wrong said a solution like that…
-
If you've got a small finite list of customer names, then you should put them in a list. Then the gadget will work. Unbounded fields don't make sense. What happens when I've got 10 distinct customers and a lot of bad spellers/readers/typists? I end up with a long list of duplicate entries. It doesn't work, because you're…
-
The fields have to be "statable", which is a dodgy word meaning simply "can be counted". Mostly means select list type fields, by which I mean you can look at a list, like the seven colours of a rainbow. Then you can count usage - "we've got 3 blue issues, 2 orange ones and 92 green". You cannot really do that usefully…
-
This is something to raise with Atlassian support. We're end users like you and have less access to your hosted system than you do.
-
Give the field a default value, then make it mandatory.
-
I don't understand why you're exporting if you want to import. For importing data into OnDemand, start by reading https://confluence.atlassian.com/display/AOD/Importing+Data
-
Wait, what? You're trying to import the backup you've just taken? I don't understand what you think you're doing here. I need to go back to the begininng. Are you trying to get data OUT of OnDemand, OR are you trying to get data IN to OnDemand?
-
What does that mean? You've not got the data? You are struggling to import it? What are you doing, and what docs are you reading?
-
No, you can export it, as above.
-
Yes. See https://confluence.atlassian.com/display/AOD/Exporting+issues with the limit Timothy mentions