Comments
-
You get that error page because there is an error in the service being run. What does the error message tell you the problem is? Have you followed any advice given in the error message? If it's not giving you anything to work with, can you read the <jira home>log/atlassian-jira.log file to find out the detail of the error?
-
Please read the original answer instead of repeating the question.
-
Ok. The problem here is that there is no code in Jira that can do that in the background. Workflow changes can only be done by administrators changing them, or changing the items they call out to (mostly, just status) The only way that the changes to the Gtrack flow would affect other workflows is if a status was shared…
-
Backlogs are not a function of projects, they are part of a board. To get one backlog across two projects, simply include both projects in the one board (Note, this can only be done with Software boards, not the project boards that are in Core "business" projects)
-
You cannot get to the database on Cloud, either directly or via an add-on.
-
The problem you describe will happen if you edit status while you're editing a workflow. If you are just selecting different status in a workflow, it can not affect other workflows. To fix this, I would go to the ISD workflow that has changed and look at who last edited it, as if you were just selecting different status in…
-
No. An issue type scheme is a list of possible issue types, which doesn't make sense when applied to an issue type. The issue type scheme tells a Jira project what issue types are available to be used in the project. You can have many different issue type schemes, and each project can either share one or have its own. The…
-
The problem is that you've not realised that the designed behaviour of Jira will do this. This is not uncommon - the later versions of Jira seem to make this less clear to new admins, and a lot of people don't see it at first. Status is shared object that a workflow refers to, it is not part of an individual workflow. When…
-
Ok, let's break it up a bit. What do you get from * issuetype = incidents and resolution = Unresolved * issuetype = incidents and resolution = Unresolved and watcher = currentUser() * issuetype = incidents and resolution = Unresolved and watcher != currentUser() * issuetype = incidents and resolution = Unresolved and…
-
You've not added the attribute to the url.
-
No. A post-function is too late to block a transition, the only way to halt it in a post-function is to crash out, which can leave the data broken. If you need to do things in a post-function that might fail, then do them, catch the error and let the transition complete, but put something on the issue to say "this failed -…
-
Go to the board configuration, then click on the filter. Edit it down to something that can work.
-
Oh, you could be, that sounds about right for an off-the-shelf Jira. It's not the tables that are the problem though, it's the logic you'll need to extract what you need. Random example - imagine an issue with a summary, assignee and three components set. A simple read of just that data and nothing else needs 8 joins if…
-
>So, I want them to be able to transition their work through the workflow Ok, that's the exact opposite of what you asked before, but it is also possible - If you want them to transition but not move them up and down the backlog, then do NOT give them schedule and edit, but do grant them transition.
-
<sigh> Wrong, the doc covers the question asked.
-
The hardware specification for Cloud is irrelevant to you - it's set by Atlassian and they don't change it or tell you what it is. You're buying the service, the hardware is up to them. For AD on Cloud, see https://www.atlassian.com/enterprise/cloud/access
-
This is a spectacularly bad idea. Jira databases are not a database, they're just a data store, and they simply are not built for reporting, and you should be looking at Apps that improve/add reporting and understand the data for you. Or even, just using the REST API. (I've managed to build a query that needed 200 joins to…
-
For Atlassian services to function correctly behind a proxy, the systems running them need to know that they are being proxied, so you need to configure them on the service side. You cannot do that to Cloud servers.
-
Try "watcher != currentUser() or watcher is empty"
-
It's not badly misleading - Tasks can sit beneath Story in Jira. It's about the configuration though. It would be better to think in layers. Epic is one layer, Story a second layer, and sub-tasks third. But there can be many issue types in the Story and Sub-task layers. By default, Jira creates issue types called Story and…
-
Which "site builder" is this? (It's not a native Confluence function, we need to know what front-end or app you are using for it)
-
That's complete nonsense. I'm a "member" of Wikipedia, but I'm not automatically watching all 5.7 million pages in there. I think you should ignore the source of that Q&A, if they're that badly wrong on this subject, there is a very good chance that they are wrong on everything else they might tell you!
-
Ah, yes, you are on Cloud - that does not let you change the landing page for the link in the header. I am sorry, but I don't think there is any way to do this on Cloud.
-
To remove it, you would need to hack the core code that causes it to be displayed.
-
Which "popup window" is this, and where is the validator placed in the workflow exactly? (Which transition, and where does that transition start and end?)
-
Ok, use a Behaviour that is an "initialiser" and says def descField = getFieldById("description")descField.setAllowInlineEdit(false)
-
It might not be possible on Cloud. When you go into administration, do you have "further configuration"?
-
What is the trigger for the script? How is it being called?
-
Yes, but my code includes target="_blank" as a url attribute. What have you been putting in the url field?
-
If it works from localhost, but not on an ip address, then that ip address is wrong or being blocked by your network You will need to enable the route through your network, allowing the traffic through from your client to server - check all the firewalls, and that selinux or other security systems are allowing access to…