Comments
-
Neither version should hide the upload add-on button, so there's a big question on what you have done to disable it. Could you tell us exactly what versions of JIRA you are using? The full version string from the bottom of the pages?
-
This is a very old thread. But yes, up until JIRA 6.4 I think, when an explicit "transition permission" was added to JIRA
-
You can add as many as you want. You can also group them with AND/OR So for your current comment, you'd add: Assignee only People in the role of project adminstrator only Then make sure the list is set to OR
-
Arg. Is https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy really that hard to find? (Not having a go at you Rafael, it's just this gets asked almost every day, so there's either a LOT of people out there who are too dumb to use "search" or "google", or there's something very wrong with that doc…
-
What version of Service Desk have you installed? What's the "CSAT plugin"? Marketplace search doesn't find anything.
-
Ok, so, what are the differences between an issue that works and one that does not? I think the date thing is a bug, but I'm not sure (and I don't see it in the OnDemand I've got access to)
-
Sorry, that doesn't really have enough information to explain what your actual problem is. It's clear some issues behave according to some pattern, and others do not, but "the remaining estimate / original estimate" is only part of a description of the pattern you mean. I can't begin to guess what you're talking about,…
-
Don't worry about the attachments - you take them separately from the database and they don't change format. I'd definitely use a mysqldump to clone the database - just make sure the Confluence is stopped when you take the dump (or you're replicating and able to dump the slave copy while replication is stopped)
-
I've seen this a couple of times. It can happen if you add a plugin of some sort to Confluence, use it for a while, and then remove it, without deleting the data that uses the plugin. When Confluence tries to run the backup, it's reaching out for code to handle the data it finds, and going "bang" because it can't find it.…
-
"Resolver" sounds like it is a custom field as it's none of the system ones, so yes, you can set it in a groovy listener.
-
You can put the "change issue team" in the notification scheme, as long as it is a "group picker".
-
Soap was deprecated in JIRA 4.something, and removed completely in JIRA 6.4. Your application needs to use the REST interface if it is to talk to JIRA 6.4 or higher.
-
You definitely need to raise this with the authors. One thing that sticks out to me in the logs - com/opensymphony/user. Jira has NOT used that since 4.2, so my instincts are screaming that you're using a plugin that is for 4.2 or lower. It may be that the plugin does things with opensymphony internally, but I'm not…
-
You have not explained what your "target process" is. And in JIRA Software, the cards are configurable
-
Jira has a lot of functions, which is great for power and flexibility, but it makes the documentation really hard work. It can be really hard to find what you're looking for when you haven't been given the right words to look for. I'd have struggled to find "watchers" as well.
-
That's pretty much the story for "watching issues" - see https://confluence.atlassian.com/display/JIRA/Watching+and+Voting+on+an+Issue (and ignore the voting bit)
-
There is a flag you can put in a properties file to re-enable the excel exports, but that will go away eventually, so best not to rely on it. Try adding jira.export.excel.enabled=true to <jira-home>/jira-config.properties (you may need to create a new file for it. Plain text)
-
See https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html
-
No, there's no way to do this. If you wanted, you could investigate amending the core linking code to add such a check, but that's a lot of work (and I'm not sure the requirement is actually that useful - how do you link to duplicates or refer back to useful tickets?)
-
Whatever the url of the JIRA you are trying to use it with is.
-
No. JIRA does not do sub-task of a sub-task You could try the Portfolio add-on to get layers above/alongside Epics, or the Structure add-on which does something that makes it look like you have layers of sub-tasks.
-
Check the field configuration for the sub-tasks, and ensure that does not hide the "time tracking" field. Then go to the project "issue type screen scheme" to identify what screen schemes are in use by the sub-tasks. Inside those, there are a list of screens in use - make sure time tracking is added to the create and edit…
-
Yes, you need to apply the scheme to the projects. This is not something that should be left to the users, they *will* mess it up. Most of my jobs in Jira have started with "please undo the mess made because we let people do what they want". Although I'd agree with you on the "let SOME users have project create, and let…
-
As a one off task, create a "workflow scheme". These say things like "In a project using me, use workflow AA for issue types 1 and 4, workflow BB for issue type 2, and workflow CC for all other types by default" (The most simple case is "default = my workflow") Now, for each project, select any of the project types - I'd…
-
Are you using Cloud? Where you can't install standard addons from the marketplace?
-
That's not a function of JIRA, it's your browser that chooses what to do with files you ask for from sites.
-
Download it by clicking on it, and then use "open" in SSMS or "open with" in the file manager.
-
That has nothing to do with conditions. Post-functions update data on an issue during a transition, have a look at those. (Although you can't do "assign to a group" anyway, so that's not going to happen)
-
No. A condition prevents a transition from being offered to the user, based on information on the issue and the users profile (and other stuff sometimes). On create, there's no issue to work with, so there's nothing to apply a condition to. Permissions to create are what you need to look at, and then you can apply…
-
You'll need to find or write a listener that can pick up any changes to task 1, iterate over its links and go update the dates on the other issues.