Comments
-
You can't "push" to people's browsers in html, without providing some code that will listen for commands and ask for the new data and kick off the redrawing automatically. This can get quite intricate. It is however, a doddle to put in code that will make the browser refresh regularly. Add this to the "head" of the pages…
-
Not really, as you can't install plugins on OnDemand that could provide any form of "quick move" The best you can do at the moment is to make sure that the configuration of the issues in the source and target projects are as similar as possible. For example, the target project should contain all the issue types and fields…
-
Have you tried the CSV importer?
-
Could you explain which importer you're using and make sure there's at least a header and one data line in your CSV?
-
I'm not very experienced with performance tweaks outside Jira, as I've always had the luxury of being able to call on proper java developers/admins/hackers. When I've run into performance issues and not been able to optimise inside Jira, they've asked me for more info. As they start to talk about heap sizes, garbage…
-
Only by amending core code. However, this bookmark leaps out at me for the second question, and I suspect is a pretty good start on the first: https://developer.atlassian.com/display/JIRADEV/Plugin+Tutorial+-+Adding+Content+to+the+JIRA+View+Issue+Page
-
Generally, you can't do large jumps, and you do need to read through all the release notes for the main releases when you upgrade. In this scenario, you should * Read the release notes for 6.2.something * Read the release notes for 6.3.something * Read the release notes for 6.4.something * Upgrade from 6.1 straight to the…
-
You don't. Parts of JIRA 7 rely on the REST API, so the option to turn it off has been removed. It's always on.
-
Ah, yes, if you pull Jira's database out from underneath it (changes to the database server will stop and restart the service), it often struggles to reconnect. Simply refreshing the connections (by restarting the application) is required.
-
Duplicate of https://answers.atlassian.com/questions/11960471
-
Depends on the plugin. Most, if not all of them, you'll have to take apart and recompile with changed styles.
-
Yup. I suspect it's a hangover from when you couldn't change workflows, but I'd like to see it (gradually?) separated so that you've got actual permissions and a second block of "flags you can use in the workflow but don't have any effect outside it"
-
But they do have specific permissions - you add conditions to the transitions. It is not obvious for new admins, and adding confitions is something I continue to forget to do when creating workflows, even after years. But I can't think of another way to do it. You can't do it in a scheme because almost every workflow will…
-
Mmm, but that's my point - each transition is unique, so you can't have a set of permissions for them. You wouldn't gain anything from it. Although, I can see the point of a condition that does something like "and project matches these criteria". To make a project fully read only, you add conditions like "users must be in…
-
I'm afraid that's all you can do. Browse permission really does mean browse. It just lets a user read an issue. The transistions in a workflow are separate from that, and by default, are unprotected. I wasn't clear on "edit" though. "Edit" in a general sense does mean "changes data", but in Jira it is more specific - it…
-
Transitions aren't editing the issue, they're separate. Open up the workflow and find a transition you need to protect. Look at it's "conditions". You will probably find there are no conditions, which means "anyone can do this". You want to add conditions like "user is in role of developer", "user has a certain permission"…
-
Duplicate of "Error rendering 'com.atlassian.jira.jira-view-issue-plugin:activitymodule'. Please contact your JIRA administrators.". which has more info
-
Yes, you'll be able to upgrade to any version of Confluence released before August 2014. I don't expect the licence file format will change either (it did between 2.something and 3.0 I think, but even then it was just a case of "licence is valid, please give me the version in the new format")
-
Did you stop Jira, run the SQL, restart Jira and then re-index it when you made the change? Jira caches stuff, so you can't run SQL safely while it's running, and hacking the database (for issue data) always means the index goes out of line, so you absolutely need to re-index. If you have re-indexed, then I'm not sure what…
-
Have a look at "global permissions" and see which group(s) have admin rights. Put the new user into that group, then ask them to remove you when you leave.
-
Ok, great, he's now a full JIRA user too, so he has two ways to raise issues. As a customer, he can use the Service Desk portal. As a JIRA user, you'll need to make sure he has "create issue" access in the project - check the permission scheme for that.
-
Customers don't get project level access, they only get to use the portal - does that work ok for Greg? If you want him to have project access, rather than portal, you'll need to add the account as a project user, not just a customer.
-
Administration rights are for administration of the system in general, not specific projects. Take a look at an existing project's permission scheme. Does your account match the rule for "administrate project"?
-
Ah, the ordering system is down - you can either wait for them to fix it, or ping them on the link given to chase it up (I'd do the second personally, in case it's something they don't know about already)
-
Get a new licence key for 250 users (or keys if you have add-ons) and apply them to your system.
-
As a starter though, the answer is yes - because Jira can use LDAP for users, it can definitely read/write LDAP. But there's no code for reading anything else, so that's what Jobin has recommended. If possible, I'd be tempted to re-use an existing connection settings Jira has for the user base.
-
You might want to show us the .vm you have modified to begin with.
-
Duplicate - https://answers.atlassian.com/questions/33571/issue-order-plugin-for-jira-v4-4
-
Ok, then there's two more things to do1) A 500 error actually implies that your application is trying to hit an invalid url in JIRA. But as it's churning for ages, it suggests it's a url that JIRA is trying to process and eventually saying "no" to. That's why I suggested that JIRA might be logging the problem. You'll need…
-
Ok, then what is the JIRA log saying the error is?