Comments
-
You'll need to find or write a listener that can pick up "issue assigned" and "issue edited" events (then it can basically run the same code as your post-function, although it'll also need to re-index the issue as well)
-
JIRA already supports it, but it's not available on Cloud. I don't think Atlassian support will do this, but there's no harm in asking - raise it at https://support.atlassian.com
-
Sounds like you're suffering from "fielditis" - a common affliction for JIRAs where unnecessary fields have been allowed to proliferate to the point where they start to clog things up. Ideally, you want to review your field usage back down to sensible levels. But, in the short term, there's a little trick for this one -…
-
The 20h looks like an estimate, which JIRA knows to format as 20h, but your custom field looks like it's either a number or it's something reading the estimate and getting the underlying data, which is storied in seconds. You'll need to explain the config of the custom field for a more techinical answer, but it does come…
-
It was merged into the Script Runner add-on many versions ago. See https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/server/overview
-
Still don't know what you mean by ANS You'll need to explain the rest of the question in more detail. There's not enough information for an answer.
-
Autonomic Nervous System?
-
What do you mean by "integrated"?
-
Check that the field has the right "context" - by default, under Admin -> Custom fields, you'll find it is usually limited to a couple of issue types. You may also need to check that it is on the create, edit and view screens for the project and issue type (project admin -> Issue type screen schemes)
-
Again, check the permission scheme.
-
The permission scheme for this project is not set up to allow your account any browse rights. Check the default permissions
-
What is the error and have you checked your logs for more details on it?
-
Yes. See https://confluence.atlassian.com/servicedesk025/managing-collaborators-754977407.html
-
Getting a partner in makes it a lot easier Your admins should be ok with an upgraded system, they'll need to read up on the changes from "JIRA + add-ons" to "JIRA is an application platform" so they can handle the users, but there's not a lot that they won't be able to pick up straight away if they're familiar with 6.4
-
There's quite a lot "under the hood" structural stuff, but generally, you'll find your users jumping from 6 to 7 won't be too shocked. Stuff doesn't move around too much, issues are still issues, projects are projects and so-on. I think the only two I've been questioned on is "where did the issue actions menu go?" (over to…
-
You'll need a bit of code to do that. There are a load of add-ons that can do this in varying ways. If it were up to me, I'd use the Script Runner to create a "scripted field" that concatenates those two together, but that's not quite the same as poking the calculated value into a custom field (with a bit more work, you…
-
You do need to raise this sort of thing at the Jira url you tried (why can't you log in?) And raising the same question again doesn't really add much to the conversation I'm afraid.
-
It's well buried, but https://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+JIRAcovers it. (To save you a bit of time, it's fine - as long as you're on Jira 4.3 or above)
-
Not yet - the best you can do is swap the project to a read-only permission scheme and minimise the usage. Just need to remember that if you limit "browse", then the project will be completely invisible to anyone without "browse" I do however know that Atlassian are working on a more robust archive - aimed at their larger…
-
Yup, spot on with the language packs - start at https://developer.atlassian.com/display/JIRADEV/Customizing+Text
-
It has no way of knowing what projects you might want to use until you submit the jql. Even if it did, it w pulls have to parse each project for the workflows in use, then each of them to establish the possible status. Which could make it unusually slow.
-
In other words, April - you've got a couple of months left ;-)Note that if you're upgrading to a supported version, the support covers that, so you can still get help with the upgrade from 5.2. Also, they're really friendly. Even if you're not supported, they'll still try to help you if something goes bang.
-
No, the situation has not changed. You need a unique url, Jira doesn't have a way to do that yet. I don't know if there's an improvement request to allow aliases (I think the most simple solution is to keep the current ID system, but have Jira recognise the full name of the board and redirect you when you land on it). Have…
-
I'm not quite sure how - if you need to see rapid board 239, then you want a url to rapid board 239 - myprojectscrumboard could be anything, and worse, meaningless to anyone who isn't working on exactly the same thing as you. Urls need to be distinct for what they're for, and you'd need to think through exactly how you…
-
No, there's nothing in Jira to do that. It's not really particularly useful
-
Screenshots it is then!
-
You can use "export to xml" to get a copy of one downloaded. Or export it to marketplace export Those might not be helpful, but you've not explained what you mean by "snapshot", so there's not a lot more I can tell you.
-
No. Mostly. I'm assuming by "milestone" you mean a Jira version. Two problems - first, an issue can be tagged with more than one version, so you'd need to think about how you handle that. Second is that you're going to need to find or write a bit of code to implement this facility. I can't see it being horrendously hard,…
-
No rules broken, but yes, you've missed something (which is horribly easy to miss). Transitions have "conditions" (also, validators and post-functions, but they aren't what you need here). Conditions are a simple yes/no question which determine "can a user do this transtion". When you create new transitions, you create…
-
I suspect the second part of the error is a red-herring, and it's the first part you need to concentrate on - do you have "M_E_Test" on the page with the data you're trying to fetch?