Comments
-
Greenhopper is the original name of a plugin which became Agile, and then evolved into JIRA Software. So there's no "better to use", it's the same thing. The code still refers to greenhooper because no-one has refactored it for a new name. The greenhopper call you've found is fine to use. Greenhopper is obsolete, it's just…
-
Are you installing it from "manage applications"? What are the first lines in the log after you click "install"?
-
Ah, from memory, the SOAP interface never gave you the estimate stuff. You either have to write your own add-on to expose it, or upgrade to using REST
-
See the workflows part of https://confluence.atlassian.com/servicedeskcloud/configuring-request-types-and-workflows-732528910.html I suspect the changes you've made to your workflow have broken the JIRA to Service desk workflow mappings, so you need to re-do them.
-
Either could be used. I would check which one is more heavily used. First rename one of them so you can tell them apart - like having "Story Points" and "Story-Points" Then run a search for "'Story Points' is not empty" and a second for "Story-Points is not empty". If one of them has 0 results, you know which one to get…
-
If it's getting nothing back at all, that is very odd. We can see it's not. Can you visit that url in a browser? Does that give you any response at all?
-
I think the board admin would naturally look to the board configuration for this. Good idea!
-
There is no user impersonation on the Server versions (generally admins are expected to understand things well enough that they don't need to). Several add-ons implement the function though. Obviously, ScriptRunner is the one I lean on, but there's an explicit "su" plugin on the marketplace, and I'm pretty sure several…
-
I really like the four Epic filters you've done there. Probably a little bit of overkill, but also I find myself filtering for unusual Epic sizes as well as unestimated. Imagine you've got 50 epics, with a mean average size of 100 story points. An average doesn't tell me much, I'd like to be able to pull out the epics that…
-
I don't think there's another way to implement anything. You could do stuff on the front end - injected javascript or Behaviours from the ScriptRunner add-on, but that would run on the client side, and by easy to bypass.
-
Validators are for checking fields (and other data) before committing a transition. You'd have to implement a whole new structure in the workflow engine in Jira. Why is this such an issue? Most administrators won't use a validator that isn't relevant to their process flow, and even if they do use it in the wrong place, all…
-
Yes, importing into a working confluence will be fine.
-
Sorry, work around what? I don't understand the question. You use a validator to check the user has put data in fields that matches your rules.
-
If this has been triggered by a workflow change, then it's likely that your new workflow does not take account of the service desk functions around "with customer/with you" flags. Check over the workflow / request configuration section of the SD admin.
-
This can't be done. Create permission is done at a project level, not issue type. There are some workarounds involving the Behaviours module in ScriptRunner, or javascript tricks, but they're inconsistent and won't completely block a user from creating the "wrong" issue type.
-
I would say there is a condition on your to-do -> in-progress transition that says you cannot perform that action.
-
People who have used Confluence before may expect those functions and want to use them. I think your requirement is broken really. There's no benefits to doing what you suggest.
-
You will need to read your log file to find out what is going wrong there.
-
Looks to me like your curl command is wrong, not the data. Try using it as documented, with -u for username and password, and the url as a distinct item. Also, what errors are you getting? "Nothing happened" does not tell us anything.
-
I don't think this is a useful thing to do. Why would you want to remove the shortcuts? As you've got "anonymous" as read-only, it's not like the users could do any harm with them.
-
Quick filters are for filtering the issues on the board. They do not change the scope of the board filter, they hide things that are on the board, allowing users to drill down to or concentrate on specific parts of the board. You need to create a new board that uses your quick filter as its filter.
-
We can't see the images. Please tell us what the errors are?
-
You should use whichever one suits you better. It's probably going to be determined by your choice of development software though. If you are using Bitbucket Server, you will use Bamboo. If you're on Bitbucket Cloud, use pipelines. This is because there's no Bamboo Cloud, and no pipelines on server.
-
Disabling functions by hiding them is not the right way to approach this, as a user can always waltz around them. You should be using permissions to control what people can do. There's no function for changing the behaviour of keyboard shortcuts, on a user by user basis.
-
For Server, see https://confluence.atlassian.com/adminjiraserver070/advanced-workflow-configuration-749383189.html#Advancedworkflowconfiguration-customisingtransitionsonviewissue and look for opsbar-transitions For Cloud, you can't do it yourself, but you can ask https://support.atlassian.com/contact to do it
-
What is your question?
-
Two servers won't solve this problem because there is no cross-server search. They are separate systems. You should do this on a network level, not with the applications. Talk to your network teams about how incoming connections are routed and how best to authenticate people coming in via the different routes.
-
Isn't it in /confluence/conf ? I've never needed to mess with that myself.
-
WAS only works for a small handful of system fields at the moment. I can't think of a simple way for you to revert, beyond sticking a backup into a development system and searching that for any changes you might have made in error.
-
No, there's no way to do this. Once an add-on announces one of its modules as a validator, it goes on the list of available validators. I'd add code to the top of your validator to say "if called in the wrong way, return a "pass"", and put something in the description to tell admins when to use it