Comments
-
Hmmm, Luiz Carlos said that was not case. Still having then issue. Add crowd.properties it goes away, remove uit an no on can log in. Luiz Carlos opened https://jira.atlassian.com/browse/CWD-3030 to allow seraph to leverage DB for SSO authentication.
-
Yes. Confluence Admin > User Directories > Additional Configuratino and trroubleshoooting > Directory Configuration Summary myserver.com/wiki/plugins/servlet/embedded-crowd/support/directories "application.name": "confluence" "application.password": (not shown) "com.atlassian.crowd.directory.sync.issynchronising": "false"…
-
I would not modify except as a last resort, because you will need to repeat anytime you upgrade.
-
Not the full line, but I think 4 or more hyphens or line-scores is seen as a new line. You can try disabling that to verify, but you would get all previous comments in a thread. You can also choose " Add a comment before a specified marker or separator in the email body and define your own regexp for the seperation (but I…
-
You say you are using the "Create a new issue or add a comment to an existing issue" handler, do you have the "strip quotes" checked?
-
It would be must faster/simpler to start fresh and re-install the user plugins. Even if "deleted" JIRA will keep a history that a project once used key XXX, and will never let any new projects use that ID. There is not any magic way to cleanup workflows, fields, etc, and would all need to be done manually, section by…
-
Sorry if I am missing something, but doesn't {noformat}*Location:* {metadata:Location}Germany Rm 938{metadata}.{noformat} get the display results you want?
-
That looks right, are you generating the results from the issue navigator as directed here, and just appending the field parameters? https://confluence.atlassian.com/display/JIRA/Displaying+Search+Results+in+XML#DisplayingSearchResultsinXML-fields WHich version of JIRA?…
-
Dashboards are for display, not data entry. You need to add a custom field to your project/issue types. Call the field "3rd Party Case Number", or whatver makes sense. https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field Next create a filter using where the new field is not empty.…
-
is this related to bonfire?
-
The throttel connections is likely just slowing down the time it takes to get to the conflicting changeset. Try this, * Shutdown fisheye and clear the cache (you can move to a backup directory instead of deleting). * Restart fisheye. https://confluence.atlassian.com/display/FISHKB/Cache+Errors+After+Upgrading+FishEye
-
Not sure how much farther it gets you, but theire is also the ability to search future sprints/ Maybe you can do what you want by using an inverse search on future sprints. not(sprint in futureSprints()) So to exclude all non-open Scrum tickets, I would think: not sprint in futureSprints() and (sprint in openSprints() or…
-
I found a solution that works in Crowd, assuming the concatenation you are looking for matched the fields specified in "first name" and "last name" fields. If crowd is given an attribute it can not find, it will fall back on concatenating first and last name.
-
Would love to see this too. Our enterprise LDAP server admins never update displayName, and so it uses maiden names and other outdsated information where as givenName and sn are always accurate. I know other tools allow values like {givenName} {sn} for the attribute to concanate, but this made Crowd blow-up.
-
This would typically require a backend database change, so I can think of 2 alternatives for OnDemand. 1) Submit a request to support. They may be willing to update the data table and reindex JIRA for you - https://answers.atlassian.com/questions/141323/is-it-possible-to-rename-a-label 2) Use the "Bulk Modify" feature to…
-
Sounds like you are trying to fight the inherent design, which is just gping to make life more difficult. Why not use a combination of versions and components to manage the status of a patch, and some custom dashabords to show progress. (Built-in Version reports are also great)
