Comments
-
You will need to make a copy of the workflow, edit it and add the transitions (make sure you add at least one outgoing transition to every status), then put it in a new workflow scheme, and migrate the project over to the new workflow scheme. It's a silly looking bug in the workflow editor, but there are some horrid…
-
You've missed the instructions about amending the server.xml in the docs. See https://confluence.atlassian.com/adminjiraserver071/integrating-jira-with-apache-using-ssl-802593043.html
-
No, you need to be an administrator to set up the project. An Agent can only configure the portal, queues, and rest of the Service Desk stuff.
-
Change what? The url you are using in the browser, yes. Not the proxy.
-
That's the current trend in web site logins. I'm not fond of it either. (Then again, I'm not fond of username/password at all. Although if we must, id/tab/pass/secondary-partial-pass/enter is definitely better)
-
Your proxy says / http://domain.com:8081 So that should make it available on https://jira.A.domain.com
-
>I'm not sure I understand your comment "an estimate on a sub-task is useless", >Again, all I want is for my team to receive credit for the work they have diligently completed. Please provide guidance on the right way to proceed here. Both of those go back to the fact that there is no "partially complete" in Scrum, you…
-
Not bookmarked. You'll find it's the first hit on any search engine
-
Pick one of them to move, shut it down, and then use the Atlassian documentation for "migrate to another server" to move it to another application server.
-
The code for the board displays is currently like that. That's about it really.
-
Looks like the user you are using does not have access to that project (remember, Admin rights mean Admin, not "arbitrarily access everything"). Or it doesn't exist.
-
Ok, so set up the transitions and apply appropriate conditions to them.
-
No, a label is a simple tag for an issue, it's really not for arbitrarily forcing more information to be added.
-
This implies that when you update (or create?) an issue, the index is going out of sync with the issue. This is quite hard to do unless you've got code interfering with the process. Could you check what post-functions, automations, listeners and so-on you have that might be breaking the create/update of an issue?
-
To be fair, they do explicitly state that you have no access to hacking the code behind a Cloud install, and that space layouts are not editable. It's on the "cloud restricted functions" mentioned when you sign up.
-
This is not strictly the "edit issue" screen, it's a board display of an issue, where there are some edit options. It's not currently possible to change the layout of the board displays.
-
One of the reasons Jira exists is that assigning things to many users does not work in real life. You should always have one single person with ultimate (current) responsibility. It's then fine to use multi-pickers and/or group pickers to show "other people who may be partially responsible".
-
This is wrong - you can not assign an issue to a group.
-
Yes, you raise requests via the portal. If you want an agent to raise an issue without a request, get them to click "create (issue)" instead.
-
Download Jira Server and install it on a machine you own. Get an evaluation licence for it and then add whatever add-ons you want to try (also with evaluation licences)
-
Ok, yes, it is inconsistent, but it's because there's two different products anticipating two different ways of working. Plain Jira adds up sub-tasks to their parents. It always has (since Jira 2 if memory serves). This is because in a waterfall-ish project, you do break up issues into sub-tasks, for several reasons, and…
-
That looks like something is wrong with your database setup, or possibly a fault in Weblogic. Confluence is not supported on Weblogic, so all I can really suggest is that you migrate to a supported configuration and try again.
-
No, you can have a lot. But please read my answers on the other similar questions you are asking.
-
No limit on number, but you will find performance will degrade if you add a lot. Jira expects to be used as an issue tracker, where you would rarely find more than a handful of files on any one issue.
-
No, you can create as many as you want. But I would recommend housekeeping and monitoring if you're going to add a lot.
-
It is on Atlassian's to-do list for the next-gen boards, but I'm not party to their planning or roadmap.
-
They do not support sub-tasks yet
-
Build REST calls in your PHP code, using the docs at https://developer.atlassian.com/server/jira/platform/integrating-with-jira-server/ to guide what calls you need to make. As I'm not a php developer, I have no examples, but I do know it does REST calls.
-
I am not sure what your question is here. Also, remember this question is nearly 5 years old, and out of date.
-
You don't need any coding to do most of this, just add the transitions, screens and conditions to your workflow. I've used a condition of "not group X" to keep the example simple, but that might not be the right condition for your needs. If it is though, I would reach for ScriptRunner, as it can put in conditions like that…