Comments
-
What validator are you trying to use here? (By the way, as you're using OnDemand, no "hacks" are available because it's strongly restricted to stuff Atlassian will support. As a plus, you're always on the latest stable version - Atlassian upgrade it for you)
-
What is the question here?
-
You can use "upload plugin" in the universal plugin manager to upload anything you want. Doesn't matter if it's supported, on the marketplace or anything. You ARE supported if you do this. But only on the core side. If you ask for support, Atlassian may well ask you to disable or remove plugins before they can help…
-
Ok, those are the JIRA logs, and that's not showing any errors. Next thing to look at is the Crowd and LDAP logs.
-
Ok, what do the logs say? Any synchronisation errors or warnings with crowd/ldap?
-
Are they in the right groups for access? Enabled? Are you giving the synchronisation type to catch up with new users etc?
-
I think there are two things to look at1. You need to decide how you are going to identify things for each board. There's loads of information to think about on several of the other posts here, so I don't think it's a simple decision, and it definitely needs to be done with your users. Once you've done that, your filters…
-
Not in the way you describe. The whole point of a board is that it represents what you want to work on. By far the best way to get that list is to use a filter. No matter how you do it, there's always a filter (and almost always a dynamic one) behind the board. That said, there's nothing really wrong with your approach.…
-
Ok, this is sounding like you have some form of network or user caching issue. Jira isn't getting the information that you are logged in as user X when you try to do something, but when you try it again, it's fine. I'm afraid you need to establish a clear pattern first - when does it happen, are there specific users, are…
-
"neither area has users ability to access" - that's probably it, but it is still very unclear what you have set up. Please could you start from the basics, and stick to using the words Jira uses to avoid confusion. * Go to the project and look at the permission scheme. What does it have next to "browse"? * Once you have…
-
Again, forget the admin stuff, it's irrelevant. What does the permission scheme explicitly say for "Browse:"?
-
Admin is irrelevant to whether you can see stuff. Admin gives you admin rights, not access to everything (unless you, as an admin, change the permissions to allow admins to see everything) Basically though, look at the permission scheme for the project. You've got it set up to allow "create" but not "browse" for the users.
-
Go to global permissions and check what group is used for "admin" (may be more than one, but most times it will be one) Add the other user to the group Ask the other user to remove your account from the group
-
I suspect something similar, it's some form of hash that doesn't tell us much, but enables us to tie it to an error report or section of log.
-
Yes, as it says, send it to the support team. The number itself doesn't mean very much, it's the actual log that matters.
-
No. A board is a shared common view of a set of issues. Every user landing on a board will see the whole board, with everything on it. The main point of boards is that everyone sees the same. The best fix for this is to educate your manager - sharing the progress information is FAR more useful than hiding it. Stop trying…
-
Ok, nearly there, but... what's not happening? Assigning of the date? Or the popup of the calendar? If it's the calendar, are you using a browser with popup blockers? Can you try a different browser?
-
Yet again, what does "not working" mean? What is happening?
-
Yes, but what does it actually do? What do you get? What are you expecting? What does "functionality is not working" mean? Describe what you are doing and what is happening?
-
You'll need to give us more detail. What does \\ actually do? What has been set up for due date? What are you expecting from \\? Are there any errors or warnings in your logs?
-
You appear to have commented out the proxy lines in the apache config.
-
You'll need to explain "does not work" in more detail. Does the click do nothing? Opens a box for new location but doesn't do anything after you've answered its questions? What does your log file say?
-
Not with the JMCF - it requires numerics. You need the script-runner to be able to cast them correctly.
-
Add a "scripted field" and have a look through https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+Fields
-
I'd use the script runner...
-
Ah, the SumUp plugin is for adding up the values for one field on many issues, not accumulating fields.If you imagine your list of issues as a spreadsheet, one row per issue and one field per column, then SumUp provides "column totals". What you're looking for is "row totals"
-
Depends on which plugin you use.
-
Find or write a addon that can add them up. I'd use a calculated / scripted field provided by the script runner addon, but there are other options.
-
My clients have moved off TFS, I don't have any access any more. I'd say you should map things as best works for you though.
-
To my mind, you've answered your own question - use TFS4JIRA. I've used it a couple of times and it does the job. I know less about UseTFS, so I'd recommend comparing the two for your uses. Although there's a slightly better answer in a lot of cases - use JIRA and move off TFS.