Comments
-
Mmm, well, that rings some alarm bells itself. Does it work when you remove this hack?
-
Not as part of the application. You'd need to hack something into it to be able to interrogate the file types being attached and block the "wrong" ones. I don't think anyone has even written an add-on to do this.
-
Hmm, ok. How are you doing the "this issue has no <custom field>" thing?
-
You said you changed it when migrating, so I assumed you knew what you had set it to.
-
"It's not working" does not tell me anything.
-
It's well buried in the doc for "migrate cloud for server", middle of the page, with no particular emphasis!
-
That's because you don't get system admin access on Cloud. Try logging in as sysadmin with a password of sysadmin
-
Cloud accounts don't get carried down, other than as a minimal skeleton without passwords etc. Try logging in as sysadmin with a password of sysadmin
-
Sounds like a post-function or listener set up to clear the field out on one of the transitions.
-
I've seen this happen when someone was editing a copy of a default workflow. One of the edits they made to the flow was to rename the "start progress" transition. They did something with the i8n property on the transition, and it ended up showing their name for it on the buttons, but stuck with start progress in the…
-
That's what would need to be investigated - what class comes back and how to get the data you want out of it.
-
Trigger a synchronisation.
-
Correct. Your only cost is the planning and enabling, which probably takes a few seconds per space.
-
Enable anonymous access in the global settings, and then go to the space permissions for each space you want to expose and add anonymous access there as well. It means "not logged in" users specifically, so anyone who can see your Confluence will be able to see these spaces without logging in. I probably don't need to warn…
-
With the standard handlers, if you set a priority on the email (most email cllients let you set a "high" or "low" flag), then JIRA will set the priority of an issue higher or lower than the default.
-
What does the log file say is going wrong?
-
The standard mail handlers shipped with JIRA only handle a few fields. They will take the summary from the email title, description from the body, some limited priority information, attachments and users and create an issue in the project you have configured them for. They do not handle multiple projects or other fields.…
-
I suspect they're compatible, but the code is not handling it. When you ask JIRA for the value of a field in Java, you have to make sure you code for the right return value. A field might hand back a string, a number, a date/time, an option (select list value), a user, or arrays of things when it's a multi-select. If you…
-
New groups that are exposed to the application should appear on the next synchronisation, as well as when a user logs in and hence uses the group.
-
Inside JIRA Server, using internal or read/write external directories, no. JIRA and System administrators have access to lots of admin stuff, including create/edit/delete users. The only other layer is people who have project admin - they can add and remove people and groups in the roles of their project, but not change…
-
It doesn't look like that is a working directory - there's no "previous sync" information, which suggests it has never been able to synchronise.
-
One thing that might help as well - Agents can use "create linked issue" which can create issues in development projects based on requests.
-
Not really enough information to tell you anything here.
-
A group might exist in a directory without necessarily being exposed to the applications. One of my current projects involves a client with 10,000 users and 5,000 groups in their AD, but JIRA only sees 400 users and 50 groups because it is limited to one part of the directory. Could that be the case?
-
Well, in 7.3 it is now possible, to a limited extent. For what it's worth, we've already picked up several pieces of work for "cleaning up the mess made by project admins when let loose on the workflow", and the ability to turn it off was added to 7.4 as a matter of urgency, as it created a massive spike in support calls…
-
Jira expects parameters in a url to be quoted in double quotes, it sees single quotes as part of the data.
-
Same here. I'm sticking with it because I need to learn, but I wouldn't be surprised to find some high numbers of opt-outs.
-
Because "useful" is going away, it's going to be removed from the code, so it can't be permanent. Hopefully, it won't go anywhere until "painful" has been brought up to scratch. My opinion is that "painful" needs a lot of work as it feels like it's a design that's passed the automated unit tests but not real user tests.
-
Screens are simple in themselves, but used in ways that can be really confusing, even to long-in-the-tooth admins like me. I still find myself looking at the wrong one! When you create a new transition, you can give it a screen (leaving that empty means a user clicks the button and the change of status just happens, with…
-
No, it's because Close and Resolve are not "issue operations". There are three issue operations * View * Edit * Create All the other changes you make to an issue are part of the workflow for it. While we talk about "close" and "resolve" as pretty standard actions, they're not universal. You can easily configure a workflow…