Comments
-
No, JQL is for finding issues, nothing else. The only possible result from JQL is a list of matching issues, that's what it is built for. That said, there are plenty of reports that take a filter and do things like count results. Might be worth a look at the 2d filter statistics gadget for a starter.
-
Not to hand, but https://library.adaptavist.com/entity/count-the-time-an-issue-was-in-a-particular-status shows a good example of how to start reading the history of an issue for something.
-
No, you have to edit each permission scheme individually. Or read them and change your account so it matches the permission you need.
-
Ok, but what actually is it the data for? Why are you putting it in? And where is it going into Jira if it's not a Jira field?
-
The sprint field contains all the active sprints issues have been in (it doesn't matter if you add an issue to a sprint and then remove it before starting the sprint) You can filter on sprint, yes, naming them in the field: Sprint in ("sprint 1", "sprint 27", "another sprint") Or you can use the JQL functions for…
-
Ok, so can you walk through replicating this problem? You've talked about cloning and updating issues, but I think we need to see the whole thing (that's why I asked about the rest of the post-function - I didn't know if you were cloning/updating in there). If you could sketch out something like: * Clone ABC-123 to create…
-
Welcome to the Community! This is working as it is supposed to. I think you're misunderstanding what the sprint field is for (but that's no surprise as it's not really explained anywhere, and it's not intuitive either). The sprint field holds all the sprints an issue has been in. It is not "the current sprint", it's all of…
-
No, that's not what I said.
-
Ok, what does the rest of the postfunction do?
-
It depends on what you pasted in from powerpoint - if it's an image, then it's just a picture, there's no table data in it. If you pasted in a table in a recognisable table format, then Confluence will try to convert it to its own table data and you'll be able to edit it like any other table you'd added to a page.
-
You shouldn't be re-using email addresses for different people, it's bad practice and stuffs up auditing. If it's the same person with a new name and/or different permissions, you wouldn't remove them, you'd change their name and/or permissions.
-
Because / is not a valid character in a file name for decent directory systems. It indicates a directory. If we take a file, put it in directory "stuff" and call it "exam/ple.txt", then what you are actually saying is "put a file called ple.txt in the directory called exam, which is inside the directory called stuff" -…
-
Much as I'm supposed to be an Adaptavist and hence Scriptrunner fan, that's actually the very first place I would look as it's the most likely thing on your list to be causing the problem! The problem you are getting is because the issue's workflow state is held in two places in two different ways. When there is a mismatch…
-
I don't think there is anything wrong with your code, I suspect the transition cannot be performed because the issue isn't in the starting status for the transition, the user doesn't have permission to transition it, there's a condition stopping it, a validator is saying no, etc
-
How are you mapping the issue type from the import file? Is the target issue type at the issue level and not sub-task? Is the "other type" the default issue type for the project?
-
I suspect someone has put the resolution field on your create and possibly edit screen, so issues are being resolved as they are created or edited. The resolution field should only be put on transition screens, ones used in transitions that go from an open type status to a closed/ended/resolved one
-
Welcome to the Community! Confluence is more of a wiki documentation system than a tracker. Without trying to do anything clever, most people would probably just write a page for each event, probably creating a template so that people are encouraged to use the same format for each, and having a standard naming scheme. Our…
-
Where are you running this? And what is the rest of the script doing?
-
This seems to be out of context. Also, you can't take 7.3.4 to 6.13, Atlassian stuff does not support downgrades.
-
Welcome to the Community! Removing an app shouldn't do this, but removing an application will. They all stamp their stuff on your data (I don't think this is a bad thing - it means if you choose to go back to them, you get everything back, and if you don't, the data they leave behind isn't imposing any significant load)…
-
See @Callum Carlile _Automation Consultants_ answer, it still applies.
-
There isn't really such a thing as a "scrum job" - most people find a job as a developer, or other producer of output, and end up doing scrum because it's the way their teams have chosen to work. It's a framework for getting stuff done, not a job description or role. The closest you'll get is job descriptions that ask for…
-
Ok, that would be quite an advanced function to have in your JQL. I'm afraid Jira does not have a function that can find those issues. Scriptrunner does implement some functions that could help you here, but I'm afraid the ones closest are only possible to use on Server/DC at the moment. The Cloud functions that might help…
-
I know of a number, both in North America and across Europe. But I can't offer up names of clients. I've emailed a few Atlassian Admins at a few of them and asked them to comment here if they're ok to share!
-
No, there's no way to add a user to the groups, roles,and permission schemes that another user has been added to.
-
Um, slight problem with issue security - it will hide the story completely! Not only will your BAs not be able to edit the issues, they won't be able to even see what the story is. I would do this with workflow properties instead. You can add a property to a status that can change the permissions while the issue is in that…
-
Whitelisting only covers the whole system, you can't go down to project level.
-
Ok, but that doesn't tell us why your database is rejecting the log in. You'll need to debug the database connection - why is it not letting you log in?
-
There are two ways I've seen this done that are quite intuitive and obvious to people. Option 1 - as you've suggested, is to add a custom field for showing "yup, go ahead and do this one". Sometimes it's as simple as a single check-box, but I prefer to have a user-picker that names the person saying "yep", so we don't have…
-
Where exactly are you trying to do this filtering? "In the project" doesn't really tell me enough I'm afraid - there are lots of ways you might be viewing the project, and different displays of different bits of it.