Comments
-
Um, you really do need to tell us a lot more about the error. As an example, I could answer you with a simple "?" and you wouldn't know anything more than I've got a question. More detail please.
-
Um, you really do need to tell us a lot more about the error. As an example, I could answer you with a simple "?" and you wouldn't know anything more than I've got a question. More detail please.
-
Are you using "OnDemand"? What type of administrator are you? Jira-system, or full admin?
-
You need to read your log to find out what Jira is doing. It's failed for a specific reason, but we can't possibly guess what it is, let alone fix it from "unable to connect". Could be anything from that information - bugs, memory issues, microscopic penguins chewing bits of your computer, dodgy plugins, overheating...
-
No, and you're wrong about events and transitions. Events are thrown by EVERY change to an issue. Not just transitions. Issue commented by comments (no transition there), issue update by any change of fields (no transition there), and so on... And "no" because you need to write *something* to catch the events and trigger…
-
Simple "get you started" answer - use the Atlassian SDK to write a validator plugin. I don't know how familiar you might be with coding, but start at https://developer.atlassian.com/display/JIRADEV/Workflow+Plugin+Modules for details on writing a workflow plugin such as a validator. If you've never looked at writing an…
-
You don't. Events are fired on all issue updates. The event contains a list of all changes, so what you do is catch any issue event and look for a change in the content of the field you are interested in.
-
A couple of my clients have implemented service catalogues as Jira projects - each "issue" within the catalogue is a service, they can attach fields and link to the issues when they are doing things like raising changes or decommissioning. It's not ideal, as the interface in Jira remains quite fussy, and reporting a bit…
-
If people can comment/update without being logged in, then you definitely have allowed "anyone" access in the permission scheme. Are you sure you are looking at the right scheme for that project? Also, the other place people can do this is in the workflow. If you have transitions in your workflow, then by default, ANYONE…
-
That really does not sound right at all. I'd guess you were looking in the wrong database. You certainly aren't looking in the one JIRA is using.
-
In the application log file.
-
Ouch, sounds like you might have a damaged plugin cache. First, read the log file from when you tried the updates, and from when you're clicking the expand box - does that tell you anything? Second, try restarting Jira. Again, you'll want to read the logs from startup to see if there are particular errors in there, but a…
-
Ah, you mean "screen" rather than "mask" There's not a lot you can do with this. The work logs are a fixed feature - to amend them you have to use plugins to inject fields, or hack the core code. There may be some work-arounds though - what fields are you trying to insert, and what are they for?
-
What do you mean by "protocol mask"? Or even "mask"?
-
It's not really a custom field - it's more of a property added by the Software application (doesn't really help you with an answer, but it's an explanation of why you don't see it as a field)
-
Edit the workflow, and click on the arrow that represents the transitions, it will offer you list of options, including post-functions.
-
You also want to "clear resolution" on both "Reabrir caso" transitions, but it's the same principle and function as setting the value in Benji's answer
-
You don't. The assignee is the one single person responsible for an issue, and it should stay that way (because multiple assignees simply does not work in real life. It has to be a single person with ultimate responsibility) See https://confluence.atlassian.com/display/JIRA/How+do+I+assign+issues+to+multiple+users for the…
-
Atlassian have got a request for "assign issues to a group", they've closed it with "won't fix"
-
1. There is a group-picker, but that will list all groups. You can actually use a select list with options having the same name as the groups you are interested in and you'll be able to use it in a couple of schemes. Or you could store your groups in a database and use one of the database values select list plugins (I…
-
You can install several versions of Java and point to different ones in the environment scripts. I'm afraid Atlassian support are likely to tell you to try using compatible versions as a starting point anyway.
-
I think I'd start with the incompatibility warnings - a lot of Java stuff does this - appears to work until it runs into any incompatibilities. You should run versions that are compatible with whatever it's complaining about.
-
There are search engines that provide you with obvious links to "install fisheye". The first hits I get on the ones I tend to use are the links you need.
-
No, you don't need to stop anything while you make changes. The worst case you'll get is if you change a workflow or permission that blocks something a user was in the middle of when you make the change. However, if you're making lots of structural changes, then yes, work in a test system to make sure they all hang…
-
More contributions (questions, answers, comments and voting) get you more karma, as well as marking questions correct, and having your questions and answers voted up by others.. As that rises, your restrictions loosen as the computers begin to understand that you're making a useful contribution and are not a spam-bot. If…
-
I have 8 on mine (which are reusable, so you can have several incoming or outgoing from the same point without it confusing people), so I'm not sure what you are seeing! You can always add more transitions in text mode too.
-
You could find/write a listener that spots changes on issues, looks at the components, and sets an issue security level automatically. Problem I can see with that is that an issue can only have one security level, but multiple components, so you'll need to have some rules about which security level you choose.in is there a way to set security level for each component ? actually i have small projects within the big project , each small project has a different vendor and users . i want each vendor to only access one component and only sees that component's iss Comment by Nic Brough -Adaptavist- December 2013
-
The author "JIRA" is being logged to tell you that it's the synchronisation with LDAP that is making the change. JIRA is asking LDAP for information, someone has changed the LDAP information, so the "JIRA" user who connects to LDAP (i.e. JIRA itself, not a human administrator) is logged as the thing making the change. To…
-
Ohh, yes, the PCKS stuff on Solaris has caused me problems with other stuff. My point was that it *can* work well on non-supported stuff. Of course, your life is likely to be a lot easier if you do stick to the supported configs. Most importantly, my point was you do not HAVE to use supported configs, which is what you…
-
An internal one - it had a JDBC connection and accepted standard SQL, so it worked fine. Last I heard, it was still running fine and had been upgraded to the lastest version of FeCru.