Comments
-
Welcome to the Atlassian Community! What "configuration items" are you looking for?
-
Why? You're already going to be looking at the issue when using the URL, and displaying field data in a URL is utterly pointless - humans don't read URLs, we just click on them. What problem are you trying to solve with this? What are your people doing that leads you to think adding a field name to a URL would be helpful?
-
Welcome to the Atlassian Community! This means that either your config file is damaged, unreadable, or contains an incorrect value for the database user and/or password. Check the content and properties of <jira home>/dbconfig.xml and that the user that Jira runs as has full read/write access to it. If the file looks fine…
-
Automation can't do that - it's divorced from the UI, it does all the work in the backend, separately to whatever triggers a rule to run.
-
So you don't actually have any use for it? What problem would this solve?
-
Welcome to the Atlassian Community! I am guessing that you are talking about the emails Jira sends as the result of activity in issues (like "issue created", "issue commented", "issue moved", etc). These emails will contain links to the issue within your Jira. The email system builds these based on where your Jira system…
-
You will need to look at how the SLA is configured for the old and new issue types.
-
Welcome to the Atlassian Community! Why? What would that achieve? What page would you land on if you used it?
-
Welcome to the Atlassian Community! If you allow people access to a data set, you can not stop them copying it down to another system. There's no way a service like Bitbucket can even restrict downloads once someone has access, and, in fact, Bitbucket is supposed to be used this way - git is intended to be used for…
-
Yes. JQL doesn't really support this because it's not something people doing Scrum would usually need. It asks a question about the question - of what use is this search to your Scrum teams?
-
Welcome to the Atlassian Community! Did you leave your Bitbucket for a long time? And not pay the bill because you were not using it? Atlassian will shut down accounts that are unpaid and unused (although they do send a lot of email to the owner when stuff is not active)
-
Welcome to the Atlassian Community! It's because the varchar data type is the most appropriate one to capture the data you will get flowing from the app. It's not so much PowerBI itself, it's that PowerBI finds it easiest to understand the data it extracts best as varchar.
-
The current version of the Community platform allows only moderators to delete. It's a slightly fuzzy group - the Atlassian community owners have delete rights, but they've named a number of Community leaders as moderators as well. I am one, but I don't have all the same permissions as the Atlassian Community owners. I am…
-
Welcome to the Atlassian Community! There's not a lot of documentation on this because it could be anything. "Intermittent" strongly implies that you have network or server overload issues. Either way, the only things you can do to debug it are generalised monitoring - read the server logs, looking for errors when you have…
-
Do not do this, it will break all your reporting. Sub-tasks are a fragment of a story, and not sprint items, so Jira ignores them in estimate reporting. Strictly speaking, estimates on sub-tasks are nonsense, but if you want to do it, you need to think through the mechanics. (I don't think there's anything wrong with doing…
-
The usual cause of this is people messing with the file system after installing Jira in the name of "security". Uninstalling an app is supposed to remove the .jar or .obr file from the plugin directory, but people remove the ability to do that, either by running the application as the wrong user, or messing with the…
-
DC/Server and Cloud are totally different applications, and hence Scriptrunner is too. * You are right about the REST API - Scriptrunner for Cloud can only do things that the Cloud REST API allows it to do. SR has no access to the java API behind Jira Cloud. You do not need to script for using the REST API directly - SR…
-
Bear in mind that that requires yet another app to be bought and installed.
-
Welcome to the Atlassian Community! The only way to do this is to read the history (which you can do from the REST API) and manually match up the record of a transition with the same time stamp as a comment. Jira does not record where a comment came from (REST, transition, issue view, post-function, etc), but it does stamp…
-
Welcome to the Atlassian Community! Plugins should not be trying to read the Jira database directly, they should be using the java API to talk to it. I suspect this error is a misconfiguration of the plugin though, not a coding error. You'll need to take it up with the vendor.
-
You'll need to create several groups, at least one for your normal users and for another for contractors. These groups will need to be granted the global "can log in" permission, and then you'll need to remove "any logged in user" from all of your permission schemes, and add (ideally role based) access for the new groups…
-
I usually do this as a scripted field, but you could do it by writing to standard custom field in a listener. The core code you need for Scriptrunner is at https://library.adaptavist.com/entity/show-last-comment-issue
-
I do not see any similar errors at all. 403s and 404s are usually indicative of either a service being completely offline, or by network problems getting to them. As I can't replicate the problem, I would want to take a look at your network - could it be blocking the calls, or not resolving the IP addresses correctly?
-
You won't find a lot. Jira is a well-used Issue tracker, but most of us don't know what iTrack is. I do, I'm old, I've run into it several times, and I can tell you that Jira is by far a better issue tracker - most people refer to iTrack as a "legacy" system.
-
Please read the third paragraph I wrote.
-
Welcome to the Atlassian Community! Asking ChatGPT is almost always going to give you the wrong answer - it tends to tell you what you want to hear rather than the truth. The library you've found will work, but you do need to test it with your code.
-
Welcome to the Atlassian Community! issueFunction is a Scriptrunner function. On server, you need to have Scriptrunner installed to be able to use it. On Cloud, you need SR as well, but you also need to be using Scriptrunner's Advanced Search, the function cannot be used in plain JQL (yet - we're working with Atlassian to…
-
The rationale is simple - don't lie. This issue was part of a sprint, don't try to pretend it was not. The current sprint is a different thing.
-
I cannot work out a way to do this with Zapier (which annoys me because I think we should be able to)
-
Welcome to the Atlassian Community! Could you explain all of the problem?