Comments
-
Ah, possibly. It's a plugin providing an unusual type of custom field - one that digs right into a database and pulls information out of it. However, I don't actually think the type of field is the issue here, I think it's the basic Jira configuration that says "when it's this project and issue type, show this field". In…
-
>to fix a bug where when a ticket type is created as task but moved to an incident, the extended reporter information disappears Roll back a bit - what's "extended reporter" info? If it's a Jira custom field, and you are using the standard built-in "move issue to new issue type" functionality, then the most likely problem…
-
You can also see the answer I gave to a very similar request a minute ago - see https://answers.atlassian.com/questions/24647845
-
That sounds like you have used a post-function provided by the JIRA Misc Workflow Extensions in the workflow, and then let your licence for the add-on lapse. You'll need to remove the JMWE function, or get a licence for it. (It's nothing to do with the Script Runner)
-
You have to have the SAME field configuration and workflows, then you can just change the issue type. If there is the slightest difference, you can't edit and MUST move them.
-
I think you need support from the vendor to work out what is breaking, potentially it's a bug in the product.
-
The Gantt chart plugin is causing a problem according to that stack trace. Try removing it and re-testing to confirm it and get back to us.
-
Is there any chance you could think about your tags - if you're writing code like this then it is NOT OnDemand, as that does NOT support adding plugins. Anyway, I don't quite understand the question - what do you mean "check whether the custom field value is updated"? If it's changed, then yes, it's been updated. The…
-
Look at your workflow - there are transitions between status. Each transition has a post-function that says "Fire ... event", with the ... being replaced by a specific event name. You can edit these post-functions to select the event from the list. If you look at admin -> issues -> Events, you'll find a standard list, but…
-
I'm not aware of an add-on that provides one of these (plain JIRA does not, and I can't find an addon in the marketplace)
-
Assuming you mean "picker", then yes, there is one.
-
Stop using it and make sure you remove any payment details from it so you don't get charged if it was Cloud based.
-
:-) No harm in trying 8, but if in doubt!
-
AH! I know this one! You're using Java 1.8 (early access?), and Stash doesn't support it yet. You need to use Java 1.6 or 1.7 (ideally 1.7). See https://confluence.atlassian.com/display/STASH/Supported+platforms
-
Ok, so if 7990 isn't listening, the service isn't really starting. Definitely need to look at the stash application log file.
-
Hmm, so it can't be serving up anything over that port. Does netstat -a tell us it's actually listening? What does the log file say?
-
"Never get anything back" - timeout? Blank screen? Have you checked the SELinux settings? What does the log file say?
-
Nope. We're a community of end-users like yourself. You haven't told us what system you're using, who runs it for you, given any indication of who you are, or even a clear idea of what plugin you are talking about (A plugin to hand a Confluence connection in what? Or do you mean a plugin in your Confluence?) You'll need to…
-
Could you list all the files in <jira-home>/logs? Note that this is the data directory for JIRA, not the installation directory
-
You'll need to read the application log for more detail - "internal server error" could be almost anything. Look for <JIRA home>/log/atlassian-jira.log (although there are other logs in that directory which may tell you more too, that's the one to start with)
-
Not out of the box, although Jira exposes a lot via it's REST interfaces that you can hook into. I'm not sure it'll match what you need, but http://wiki.customware.net/repository/display/CustomWare/Connector+for+SharePoint+and+JIRA is the only thing I know of that tries to get the two to talk to each other.
-
No. The top level of admin is reserved for Atlassian support.
-
No. The top level of admin is reserved for Atlassian support.
-
Start at https://developer.atlassian.com/display/JIRADEV/JIRA+Plugin+Guide and https://developer.atlassian.com/display/JIRADEV/JIRA+Developer+Documentation and then focus on https://developer.atlassian.com/display/JIRADEV/How+to+create+a+new+Custom+Field+Type
-
Oh, yes, absolutely. If you create your own custom field type, you can pretty much do what you want with it. This also has the advantage that it does the security work before data goes to the browser, so there's no leaking of potentially sensitive data, probably no need for any javascript, and no way to bypass it.
-
Nope, can't do it natively, you need some code, javascript etc. There's a more advanced conversation from earlier today that you might want to look at - https://answers.atlassian.com/questions/199057/is-it-possible-to-show-few-issue-types-and-category-and-subcategory-to-particular-group-in-jira-5-0-2
-
Start at https://confluence.atlassian.com/migration/jira-7 and yell here if you get stuck - we're not support, but we can try to help you out (and there's Atlassian support if you get very stuck and we can't help)
-
Your system rights are irrelevant, check the permission scheme in the project to check if you have "delete issue" permission. Most sensible JIRA admins won't allow delete by default, as it really does mean delete and people often use it by mistake. If it's not the permissions, then please tell us what the error message is…
-
I would say all your issues are resolved. So JIRA has nothing to show in the "unresolved" sections. The usual reason this happens is that you've set up the resolution field incorrectly. People often do one or both of: * Putting the resolution field on the edit screen (and/or create) * Add values to the resolution list like…
-
Wow, that's a lot of money for "here's a copy of last night's backup of data you own"... Oh well. :-)