Comments
-
Open it in IDEA?
-
Steven has already answered that - you need to write an add-on to inject the option.
-
The limit is there to prevent you overloading your system - the excel export is highly resource intensive. There are flags you can change to increase the limit, but I don't think you can get them changed for OnDemand. I suspect exporting in batches is your only answer here. Maybe worth looking at why you want to export so…
-
Yes you need separate licences, but it's not too painful. If you log into your "my atlassian" account and find your confluence licence, look beneath it and you'll find a link to "Generate developer licence". The developer licence must NOT be used for production, but it IS there for testing upgrades, failover, development…
-
Duplicate of https://answers.atlassian.com/questions/151868/is-there-anything-similar-to-behaviors-plugin-for-ondemand
-
Wait. Ours often whizzes through to 99% and then takes about 1/3rd as long again to get the last 1% done. Very annoying, but there's not a lot else oyu can do. I would however, go throught the logs carefully, and consider increasing logging to see if you can work out what's going on!
-
Log in as your admin, go to the project configuration and look at the schemes in use. You should be able to click on the link for the notification scheme to change it.
-
That does suggest the script runner is installed and has been given an invalid script. You could disable it in the plugins admin, but it could be being used in lots of places, not just this project, so I wouldn't recommend that. You should take note of the exact screen (your phrase "open a project" is not clear as to what…
-
I'm not sure what the question is here. Sounds like your "standalone network" has some issues, but there's no detail to work with.
-
It's because the scheme is active - you're trying to add to one with "HNC" in the name, but showing us "entregable" in the list. Look to the right of "HNC" - it says the scheme is shared by 24 projects - that's why you can't add more workflows to it.
-
Interesting. It appears that Server is ahead of Cloud for a change!
-
Hmm. Are you definitely on version 6? Check the footer if in doubt.
-
Go to your my.atlassian account and you'll be able to switch over.
-
Damn you autocorrect. Greenhopper, not grasshopper
-
JIRA Core is plain Jira, an issue tracker. JIRA Software is JIRA Core plus an additional application which is aimed at Agile users. Under JIRA six and below, this was an add on, called "agile" (or grasshopper if you are old enough) To add Software or Agile, you do need to pay, but are you on Cloud or Server installations?
-
The Tempo Team has nothing to do with project access. I think the most simple answer is to go to the project roles and add the new group into the role of "user" You'll then need to work out what is letting the group get into the Software projects - check that they're not using "anyone" in the permissions and what other…
-
Not quite - Behaviours is now part of the Script Runner as I said in my answers. Valid up to 7.2 (7.3 soon)
-
I've done all of them at one time or another. 2 and 3 I always mention because they're possible, but I don't like them. Quisapps is overkill for one field, but if you find a case where you genuinely need a lot of field security (there's not as many cases as people seem to think there are, but there are some), it's well…
-
Four options: * Get the Quisapps field security add-on. You can also do it with Behaviours in the Script Runner, or other javascript hacks, but these can be bypassed. * Find/write a custom field that you can restrict for edit and copy it into the priority, or even override the priority field * Hack the core code for the…
-
Jason is right here, you can not clear the resolution in a transition by using a screen. You need to use the transition method stated in my answer - clear the resolution in a post-function
-
It's a bit of a hangover from JIRA 1, and something I've always thought was clunky and needed changing (I'd group status together into meta-status, rather than a simple open/closed) A post-function is a workflow artefact - it's "something to run when a transition executes". There's a standard 5 of them added to transitions…
-
Please, do not say "resolution status". Resolution and Status are totally separate things. The problem you've got here is that you've customised your workflow and removed the things that were setting the resolution field when you get to the end of an issue's lifecycle. Have a quick look at the default JIRA workflow, as…
-
You can only move an issue if you have "move" permission in the project. Check the permissions. It will appear in the actions menu
-
You can only edit an issue from one type to another (i.e. use the "issue type" field on the edit screen) if the configuration for the two types is exactly the same. The slightest change of workflow or fields will disable that option (because it means JIRA has to do config checks to keep the data valid) You can always move…
-
No - you're either an admin, wiht access to change things, or you're not. Jira 4.4 does show more project configuration to non-admin users, but it's a long way from showing everything (and you probably don't want to - some admin settings can have security aspects...)
-
No, it's not changed. You go to the project, and put the group in the role you want to add it to.
-
You've got a slight structural problem with this idea too. Let's say you can come up with a display or highlight method, then how does Confluence know that it needs to be displayed? What is the rule that defines when the highlight should show? All you've said is "changed", but that covers every page that's ever been edited…
-
Look at the notification schemes. They're designed to let you send email only to the people who need to be notified. In your case, it may be easier to set up one that mails nobody, and use if for the quiet projects, and use a normal one for the new team, taking care to include only them in the roles that get emailed.
-
Not natively, but there's a "project fields" add-on in the marketplace that does a decent job of it.
-
There's no real question here - could you give us more to go on?