Comments
-
Putting arbitrary delays into it is the wrong approach. What you really need to do is build a check that one system has the data you need. I don't know what your HP system is, so I can't talk about it. (HP sauce is nice, but I'm assuming you mean a Hewlett Packard system of some sort) So, If I understand this correctly,…
-
Sorry, that makes no sense in this context. An email arrives and creates/updates an issue. Your listener has nothing to do with that directly, so I don't know how it relates. "The JIRA creation time..." sentence, I can't even begin to guess what that means.
-
You would need to write your own mail handler to do this. However, I don't think it would work well, as the handler would have to stop processing until the "specific time", which means it would then clog up all the other email coming in. Is there a reason behind this idea? Could you just not send the email until it is…
-
I suspect the migration is caused because Atlassian deploys releases into Cloud a lot and the upgrade process is spotting your markup and trying to migrate it to the new storage type. I suspect the only valid approach for Cloud is to get the Jenkins plugin updated so that it posts in the right format instead of wiki.
-
Jamie is right about Jelly - I've been able to destroy test systems with it, and I wasn't even trying that hard.
-
Ah, hang on, sorry, I really should have spotted this earlier. You have listed the content of /lib. Not <JIRA install>/lib. The driver needs to be in there, not the operating system /lib directory.
-
That's not what Jobin asked, he was asking you to check file ownership and permissions. An "ls -l" in that directory will tell us what we need (and capture it plain text, there's no need for screenshots)(p.s. No, it's not, root is the root account)
-
Yes, but they are horrid and most people don't understand them, and you can't use SQL to fix the problem unless you know *exactly* what you are doing. Please, use the integrity checker, OR try to create a new set of workflows for the project and migrate to it (as changing the workflow on an issue to anything else, even an…
-
Yes. Edit the workflow, find the transitions where you want to remove the screen, and set the screen to "none"
-
Read the worklogs on the issue. I suspect that's not what you need, but you are not being specific about it, so we can only give you very generalised vague answers
-
Do you mean for JIRA administration, or the Atlassian account you use for licences etc?
-
What does the log file say when you try to enable it?
-
I suspect there's more of a question lurking behind this one, but to answer what we have: A burndown chart is based on the board filter. If it needs to burn down on "tasks instead of issues", all you should have to do is change the filter to select tasks instead of issues.
-
If the config for both types is identical in the project, you can just put the type on the edit screen and edit it. Otherwise, you have to use the "move" option to change the type.
-
You haven't given it a valid account to log in with.
-
It's a "hard clearing of the plugin cache". The same steps can be used on Confluence, up until 5.10 (I'm not sure about 6 yet). Do NOT try it on a Data Centre install though... (That goes for JIRA DC too)
-
It's complaining about other long-running tasks, which could be a lot of things. I suspect you need to try to id them to rule them out or fix them. As a short term attempt to fix it, you could try clearing the add-on cache. * Stop JIRA * Go to <JIRA installation>/work * Move the files in that directory to a backup…
-
This install should take a few seconds at most. The errors in your log are not actually much to do with the add-on, they seem to be email related, and saying that you need to fix a couple of connections to your email server (you've configured the wrong username/password combination in one or more JIRA "incoming email"…
-
He probably doesn't have the "browse users" permission. Have a look in Admin -> Global permissions
-
The first issue, where it stops processing and doesn't pick up again does happen if there are networking issues sometimes. The second one is probably related, but it's hard to tell. Two things you should look into to begin with 1. Upgrading - you're on an unsupported version of Jira, and later ones have lots of…
-
As well as what Aron said, you need to REMOVE "browse projects" from any other groups those users are in, or any other way that they might be getting access to them. Generally, to do "only see project X", you need to re-engineer the default groups and permissions in Jira, because it's permissive and simply doesn't do these…
-
Yes, you need two separate installations.
-
I think you'll need to do some network tracing here - it's plain that your Jira cannot reach your Confluence, and vice-versa, and you need to open that up. I'd start with a look at the logs to see if they are any more verbose on what the root of the error is, and then start with the basics on the server - log into the Jira…
-
Maybe you should tell us what documentation you are struggling with?
-
It's a good question, but I can't give you a specific answer - you'll need to read up on, and try the various options to work out which one is best for you.I know it can be done with Adaptadist's Theme Builder (Yes, I can be seen as biased here, as I work for Adaptavist, but I'm saying that based on my pre-adaptavist…
-
Ok, well messing around with the dashboard template is not going to help you on that one.That view is a predefined function built into an "add on" that Confluence ships with by default. To change that to add tabs, you will need to pull out that add on, and write your own to replace it, which is not going to be pleasant.If…
-
Eh? A visual tool isn't going to help you find code that you don't know is doing the stuff you think you might want to change.Forget tools and technology. Look at the screen the dashboard draws for you. What are you trying to change in there?
-
Not really. There are some editors which will help you edit velocity, but I'm not aware of any that would WYSIWYG it. Velocity is quite flexible, so it's hard to code for known outputs. What are you trying to do with it?
-
If you mean users who are not active, then look at the last login times in the user browser (and cross check with their activity streams). If you mean the users with the "inactive" flag set (so that they cannot log in or use JIRA), then it's also indicated in the user lists. There's no such thing as an "inactive group" in…
-
It's the same answer - check the conditions