Comments
-
It is possible in ScriptRunner, but only because you can use Groovy/Java to build REST calls. Webhooks are often easier because you don't have to do all the code to generate and issue the calls.
-
The "assigned to me" gadget works off a filter that works out to be "assignee = me and resolution is empty". So the two things to check are that you are the (system field) assignee and not using some other field for assignee, and that the issues have no resolution.
-
Ok, you'll need to read the logs and check what the browser is doing as it fails to return bad logins to the login screen.
-
You should do that with JQL, not SQL.
-
Someone edited the config file after the previous time Confluence was started. They've corrupted it and it's no longer valid, so this time when you try to start it, it is failing. You will need to repair the config file it is telling you about and restart.
-
Ok, so what are the errors in the logs, and/or the errors you get when you try to reach it?
-
You might be better off trying to fix "run over https, but this didn't work", as https is strongly recommended for any system on a network nowadays. But, what you might be missing are: * Whatever in Apache might be redirecting http to https (you might not have done this, so there might be nothing to check) * The base url…
-
Yes, this is an odd one. It is logically correct, but most humans do not tend to think this way naturally and when you first run into it, it does seem odd. For any field that could have multiple selections, "is not X" means what it says - exclude things that have X in their list. But if the list is empty, there's nothing…
-
Right, so you managed to edit the workflow to add the status, then got it into the board. Good news!
-
Yes, the upgrade will overwrite all of your changes. You will need to look at each change you've made to evaluate whether it's still needed (sometimes, tweaks I've applied can go away due to new functionality in the upgraded versions), and how to re-apply it in the newer version. One thing that usually helps with this is…
-
Ok, your manager is not going to get that - the status colour belongs to status, not resolutions. Two things I would look at: * Create a scripted field that looks at the resolution and decides on colour or flag that the PM can use - I would be tempted to have it show a short bit of text that can be searched and sorted on…
-
I would be looking at 7.13 - the latest, but also the next "enterprise" release, meaning it will be fully supported for longer than most versions. You can upgrade from 7.3 to 7.13 directly, without going through other versions.
-
That can't happen, directly. The status colour is tied to the status, it has nothing to do with the resolution field. In theory, you could actually write a script that changes the colour dynamically, so that when an issue changes from <no resolution> to <resolution set to something>, the colour of the status it is in…
-
No, your licence entitles you to run any Jira versions 4.0 to 6.4 with the Agile add-on, and Jira Software 7.x. The easier way to think of it is that Jira Agile has simply moved from being a plugin to being an App, and been renamed. The licence entitlement has not changed.
-
Jira admin is complex because the system is flexible and powerful, there's not a lot that can be done about that - it has to be complex to allow you the power. (Don't get me wrong though, I am sure the admin could be improved, but I think Atlassian prioritise shiny new stuff over making it better) A status is not just a…
-
Please start by reading the log file; <confluence home>/log/atlassian-confluence.log will contain errors giving you a lot more detail on why the database cannot be accessed.
-
There is no way to do this on Cloud - all the "tricks" need access that you don't have on Cloud.
-
You have answered your own question! You say you have an "unlimited" Agent licence, so your user tier is "unlimited".
-
You can find most of it in the system information page. But I strongly recommend that you do not bother. You won't be writing to the database (with some minor exceptions, writing to a Jira database will break it, possibly catastrophically), and reading it is a nightmare because it has evolved as a data store, it simply is…
-
That looks completely correct to me. The other question I completely forgot though - what version of Confluence are you on?
-
I would run a search for all issues created in the last year ("created > -365d" for example), save it as a filter, and then use that gadget in a dashboard gadget - filter statistics with the creator chosen as the statistic to report. It will give you the top 50 creators.
-
Remove the issue type field from edit screens, and change the permission schemes so that users do not have "move issue" access.
-
Because that would give an attacker the ability to get a complete list of all your user IDs to make an attack on your system easier. However, there is also something wrong with your Jira - when a user gets the login wrong, it should return them to the login page. You should work out why it's failing to do that - do you…
-
Status and transitions are two completely different things. A status is an indicator of where an issue is in a workflow. A transition is the action that enables the user to change the position of the issue in the workflow. So, status properties apply to status, and transition properties to transitions.
-
Atlassian does not do that sort of work. I'd recommend you get hold of one of the Solution Partners - many of them do this sort of consultancy (and yes, I work for one and it is my job to do this type of work) See https://partnerdirectory.atlassian.com/ to help you find one
-
Ok. * Only fields that ask for entry are placed on the resolution screen, so you can't do this with a data field. * Yes this can be done, as long as the field is on the edit screen for the issue (i.e. it is NOT read-only) * That's fine, although I'd consider the use of a condition as well, so the transition can't be…
-
Yes. That's what defaults are for. Most users, when creating a series of issues, will be working on a set of similar things, and want to create the same thing, not have to change it every time.
-
The default only applies when a user has not created an issue before or their settings have been cleared. If they've used it before, then the system is designed to remember what they used last.
-
It should eventually load all of them, but sometimes, it fails. Trial systems are the same as full systems, there's no functionality turned off during a trial. Sometimes you just have to wait, sometimes a refresh can help. You mostly get this message when a Jira has been restarted and it hasn't loaded any of the gadget…
-
The system reads the directories in the order you put them in the directory list. Once it finds a user or group, it stops, and will ignore duplicate entries in directories below the one it found a user in. So, if you had say "nic" in ds, us and internal, everything will see "nic" from ds, and completely ignore the other…