Comments
-
A lot has changed between JIRA 3.13 and JIRA 6.3.13 and that class has changed with it. The error is pretty clear : the method no longer exists. And if you take a look here: https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/event/issue/IssueEventManager.html you can see alternatives. So…
-
Leandro,The message from the API also indicates that the field seems to be missing.It's not because you can see the field that you can edit it. Only fields that are on the Edit screen can be edited after the creation of an issue.Best regards,Peter
-
Hi Leandro, Are you using a specific Screen Scheme for this issue type? Could it be that the reporter field is not available on the Edit Screen in this Screen Scheme? That would explain why nobody can edit the field once it has been set. Some more information about Screen Schemes can be found here:…
-
Hi Aquarius, Are you basing your swimlanes on stories or something else? Does the board sub filter filter out your sub tasks (look at the bottom of the general configuration page to see the sub filter). Best regards, Peter
-
Hi Cian, Was the Confluence license updated to 500 users? Did you also update the Team Calendars license? If not that might be the problem. Best regards, Peter
-
Cian, Can you recheck the team calendars license in the add on management menu? If needed repaste it and submit it again. If that doesn't work you might have to clear the plugins cache as described here : https://confluence.atlassian.com/display/CONFKB/How+to+Clear+Confluence+Plugins+Cache Best regards, Peter
-
Hi Ilya, Did you check if your Java Home is indeed filled in? You can do this easily by going to the command line and executing echo JAVA_HOME. If that doesn't return the location you would expect you can follow the steps detailed here to set you JAVA_HOME variable :…
-
Hi Susanta, Could you take a look in the bamboo log file to see if you get any error message? the log file can be found in the logs directory of your Bamboo home directory. This looks like a configuration issue. Cheers, Peter
-
Hi Bede, Do you have the Assignable User Permission in the project the user is creating an issue in? This is governed by the Permission Scheme of the proejct. You can check this using the Permission Helper or by simply going to the issue and trying to assign it to yourself. Best regards, Peter
-
Hi Norbert, I think you should open an issue about this here : https://jira.atlassian.com. Best regards, Peter
-
Christian has a good point, if you are using your Jira for other projects too be aware of the consequences of editing the core velocity files. You could of course also add an 'if statement' that checks if the issue key is from a certain project and only display the message if this statements resolves to true. But that's…
-
Hi Samantha, By using the notification scheme in your project you can indicate that the original reporter should receive a message when the issue is closed. This message is created with a velocity template that you can find in your Jira installation directory under the following directory tree :…
-
Hi Judd, I would take a look at this page for more information : https://confluence.atlassian.com/display/ATLAS/Federating+JIRA+-+Managing+Multiple+Instances But you'll need a new license for your new server. Best regards, Peter
-
hi Steve you could try something like this : {{*/foo/\{bar\}*}} It seems to only work correctly when there is at least one more character behind the escaped "}". I would report it as a bug in https://jira.atlassian.com Best regards, Peter
-
Hi Marcel, This is not possible out of the box, you'll probably need to change the JIRA source code or write your own plugin to get this to work. Best regards, Peter
-
Mike, Are you using OnDemand or an instance you host yourself? As Rambanam points out in the comments below, this does not work for OnDemand. Best regards, Peter
-
you are right rambanam, that setting does not influence this problem in any way.
-
Hi Mike, Could it be that your external user management option in the General Configuration is set to ON ? Maybe that's causing this problem? Best regards, Peter
-
The answers from both Henning and Nic are correct. Either you use 2 seperate workflows or you use one workflow with multiple transitions between certain states using scripted permissions based on issue type. Best regards, Peter
-
Hi Hannah, Where can this group change the due date? Is it during a transition in your workflow? Then the permission might be on who can do this transition (you can see this in the transition screen of your worklow). Best regards, Peter
-
Hi Hao, It might be that you as an administrator don't have the 'Browse Users' Global permission. You can check this in the Global Permission section of your Jira Administration. Some more info can be found here : https://confluence.atlassian.com/display/JIRA/Managing+Global+Permissions?src=search Best Regards, Peter
-
Darrel, As this seems to be a problem related to a plugin on your Cloud instance and not something we can easily fix I would recommend you to contact Atlassian support: https://support.atlassian.com they might be able to help you out. Best regards, Peter
-
I would recommend you to request the latest version of IE or permission to use a different browser if this is really bothersome. There is nothing we can do about the IE behavior. Maybe one last thing you could try is using a different theme for your space.
-
Did you try it in other browsers? Do they display the same weird behavior?
-
Hi Darren, Could it be that you are running IE 9 in Compatibility view? https://confluence.atlassian.com/display/CONFKB/CSS+Features+Do+Not+Function+using+Internet+Explorer+in+Confluence+but+Function+Correctly+on+Other+Sites Best regards, Peter
-
Hi Mathias, If you remove everybody except yourself from the Schedule Issues Permission in your permission scheme nobody will be able to add issues to a sprint (active or not). That might be a solution. More information about the JIRA Agile permissions can be found here:…
-
Are you working with the Jira administrator account or with the confluence administrator account? Can you edit/move the issue directly in jira with this administrator account (it could be that there are workflow restricitions or project permissions blocking you from editing/moving the issue) Best regards, Peter
-
Hi,You need to go to the Confluence Administration menu, search for the menu item 'Global Permissions' and set the option 'Use Confluence' to 'Can Use' for Anonymous Access.Cheers,Peter
-
Please take a look at the Warning on your permission page for the Confluence Space: you need to grant the global Use Confluence permission to allow anonymous access to Confluence.Cheers,Peter
-
Does your customer have access to the Knowledge Base In Confluence? (AKA: is is searchable and viewable anonymously ?) Best Regards, Peter