Comments
-
I don't think Rusi has noticed the "Cloud" tag on the question. As far as I know, there are no add-ons available to Cloud that will create sub-tasks during post-functions.
-
It's a quiet gem of a function which stopped my only real attempt to write an add-on I could sell - I wrote something that let you search by category in JIRA 3, and then JIRA 4 did it for me!
-
You've said "see it on the view screen". You won't get that until there is data in the field. Try editing the issue and making sure there is data in the field.
-
You'll need a listener to do this (or post-function, if you want, but a listener can catch "edit" actions as well as creation and workflow activity) However, you're using OnDemand, so you can't install one.
-
You'll need a listener to do this (or post-function, if you want, but a listener can catch "edit" actions as well as creation and workflow activity) However, you're using OnDemand, so you can't install one.
-
I don't think there is - the potential lists of integrations are so large as to be unusable. It would be better if you focussed on the ones you're interested in.
-
Yes - if the integration requires changes that override, replace or add to JIRA core code, then you can't install them on Cloud. If you can do the integration over REST, you're fine.
-
Can't see any usability issues there, or with the docs. As a user, some options vanish because most users aren't admins. p.s. it's not my software, I work for an Atlassian partner, not Atlassian.
-
What function? What application? Which drop-down?
-
See https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html
-
I think the main reason is that service requests really do need to be identifiable as belonging to an end user, and you need to identify the users so you can show them only their stuff. I don't like anonymous *write* access of any form in most systems. It's fine in some cases, but not a lot.
-
Jira Service Desk requires identifiable users in order to work properly. You can't use anonymous access in it.
-
What does "are necessar to login" mean? What doesn't the anonymous user get to see? What's the error message when they try to do stuff?
-
Yes. You can just buy a new one with a new account, but if you want to do something a bit more complex, email sales@atlassian.com - they're really good at dealing with requests like changing companies, getting license fees lined up to co-terminate, and so on.
-
I don't recognise the type "import ID" - is that provided by a plugin of some sort? Your text fields - are they just "text field" or "read only text field"? What I'm getting at here is that read-only fields won't appear on Create or Edit screens. If "import ID" is a variation on a read-only text field, then it won't…
-
Ah, one more nagging doubt - What type of field is it?
-
Yes, you've missed one of four things: Screens (have to mention is for completeness, but you've got that right) Field configurations - can hide fields by issue type and/or project. Fields default to "visible" though, so if you have not touched field configs, they should be shown Field context - when creating a new custom…
-
Sorry, no, I'm going in the wrong direction there. Although I've said use the links field, it's not really a field, it's a place to capture links. You should be able to iterate through the links on the incoming issue. However, I've only ever done this with something linke issueLinkManager.getLinkCollection(issue, user) on…
-
It's a list of link objects, not a case of casting it, but iterating through the list and reading each link object for its type.
-
Yes, you can, as long as you have the "links" field on screen for them (that is only available on later versions of Jira). When your validator runs, it has access to the current issue data (which is empty for new issues) and the data the user has entered. So you can indeed iterate through all the links the users have…
-
This is exactly what workflow validators are for - they'll throw a "pass" or "fail, with error message". But those only happen in the workflow. Other events (such as comment, edit, add workflow etc) do NOT have any validators you can hook into. You can make listeners that catch them, but it's too late at that point and…
-
Do you have any links on the file or is it duplicated in some way? Has the file got the same class named twice?
-
That actually makes some sense - there was a bug in Jira that allowed people to be deleted (not disabled, but fully deleted) even when they'd made comments. When that happens, it actually blocks further updates to the comments they had made. Is that a possibility? (Newer versions of Jira block deletion of users with…
-
You're confusing properties and permissions. Start with permissions - a user can be granted the project permission to add/edit/edit-own/delete/delete-own comments. That's a general rule that applies across the whole project and is the starting point.Properties are separate. They live on assorted Jira artefacts - the…
-
It's not right - I can edit comments on closed issues, if I've got the settings correct (workflow properties, plus, as Joseph says, the right general project permissions)
-
Check the workflow status for the property that prevents issues being commented on (I can't remember the name of the property, but it is pretty clear) However, you mention that the comment contains a "script" - what is that script, what does it do, and what is it written in? There's a good chance that the script is the…
-
You may even have the most simple case - the reporter is a field on the screen, the user entering the issue has "modify reporter" permission, and they're selecting a user other than themselves.
-
Start with https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy
-
Answers doesn't really feed in to Atlassian's processes on feature requests. They DO take ideas from here and log them in their Jira (on the rare occaision that the questioners don't beat them to it!), but I'm afraid comments here carry no weight. Have a look through…
-
The document I pointed at is still valid, so yes, moving off OnDemand is your only option. Several Atlassian partners do less restrictive hosting (Appfusions, Contegix to name a couple) if you still don't want to do it yourself. Atlassian are looking at broadening the list of plugins they install and support, and letting…