Comments
-
Jira's built-in email handlers rely on the issue key (as there's no way of knowing how else you users might want to relate stuff - for some people, the same subject might be key, but for most of us it is absolutely not unique and we need to be raising many issues with the same subject) So, if you want your users to be…
-
You can link multiple services together, yes. But your story is answered by your first paragraph. Your knowledge base is selecting answers it can see, and it points to where it got them. But your users do not have access to where it is pointing. This boils down to something that reads as very obvious: You need to make your…
-
Your equivalences are wrong. When a field contains "X", then "if it = X" works, but if a field contains "X, Y" then it "if it = X" is false because it doesn't just contain X. You need to ask "if it has X in the values", not "is it X"
-
I'm afraid you don't have any choice here. You either have to make the field optional, or include it on the screen so your users can set it. Those are your only options. Mandatory/optional has nothing to do with screens. This is a flag you set in the field configuration for the issue type in the project.
-
This script has nothing about the order of fields, so it's the wrong place to look. The order is done on the screen definition.
-
I am sorry, I was not clear. What is the context the code will run in? What does a user do that makes it run?
-
I suspect the best approach would be a little bit of javascript injection into the issue view which could call a (local) REST endpoint that could then check for previous views, trigger an email if there are none, and then record the view. I don't think that would be a huge chunk of work - an App could bundle up a…
-
This usually depends on where you are trying to get a handle on the issue. What is the context for the code you are running?
-
Great idea, emphasising the contributions to (proper) discussions is very welcome! I do feel that discussions don't get as much attention or feedback as they deserve.
-
Sorry, I've been very terse there, and I do not mean to be. You are absolutely right about transition permissions applying to column moves. I should not have written my responses like that, and I apologise (I was going to edit, but I think it's better people can see why I owe you the apology)
-
The answer was from 2012, around 4 years before that was introduced. And the advice still applies - look at the permissions.
-
That is what one of the answers tells you.
-
Start at https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html
-
Ah, now you've run into the problems with sub-tasks in Jira Software. Atlassian are sticking to the way Scrum is done, where estimates on sub-tasks are irrelevant to the backlog and burn-down, and there's no roll-up to parents.
-
It has never been a problem in plain Jira (Different story if you're using estimates in Software) All parent issues have a panel where you can toggle the timetracking view between "this issue only" and "this issue and all its subtasks" Since Jira 3.something, you've been able to use Σ fields in the issue navigator to…
-
That usually means the request has run into something like a broken field, the "internal server error" is quite a generic response passed back to your REST call. You will need to look at the logs for the Jira server to see what errors it throws when your REST call arrives with it.
-
There's some things in your script that are a bit suspect, but they should all be picked up by the basic script editor built into ScriptRunner. Could you go back to your script for the scripted field and look at the editor. Are there any red crosses next to any lines? Then look below it, for a box labelled "preview issue"…
-
No, see https://jira.atlassian.com/browse/CLOUD-5915 It might be worth asking https://support.atlassian.com/contact if they would set up a robots.txt for you though.
-
The first - the system will go read-only when you add user 2001 (unless it's been changed recently and the site admin stuff just stops you doing it)
-
An upgrade won't help you, there's no "read" in later versions either. It's too potentially loading to implement. It might be ok if it were just the issue view, but there are many ways to "read" an issue, and an event would probably have to cover most of them. Do you consider a view of it in the issue navigator as read? On…
-
My guess is that your logic is broadly right, but your equivalence checks (==) are not. For example, getIssueType() will return an issueType object, not a string, so your check for "is not epic" is always going to return true. Similarly for resolution A little more formally (I'm happier in Java than groovy for this), I…
-
Before you delete it, you really should find out why they did this. My best guess is they were hiding a massive problem that they've created elsewhere. You may only be able to identify that by stopping it running, and seeing what goes wrong! But in the long run, yes, absolutely, you need rid of this completely, it's a very…
-
If you stop paying, it will last for a week after the last payment, be inaccessible for a further three, and then permanently deleted. So, no, you can't "pause"
-
Yes, it's exactly that. If you make the resolution mandatory, you have to fill it in (i.e. resolve the issue) when you create the issue, and you can't blank it out!
-
Jira off-the-shelf, just has "bug", so your system has had this flag added by one of your admins. You should ask them (or your colleagues who are using it) what the definitions are.
-
It defaults from the three coloursof the status in your workflow, but your board administrators can add more columns, rename the existing ones, or delete at will, and put different status into different columns.
-
An issue in Jira is "resolved" when the field "resolution" has a value set Nnote - it is any value, doesn't matter what it is. You could have done, won't fix, ended, fixed, penguin, unresolved as options, all mean "issue is resolved". The only content that means "unresolved" to Jira is <null>, and it displays "unresolved"…
-
Ok, while the principle of "index in another thread" is a good abstract idea, your question scares me. Why are you doing this? Indexing is not something you should ever have to think about in Jira. Questions starting with "I want to index" are almost always posted by people who are trying to do really bad things in Jira…
-
Your screen shot implies you have made the resolution mandatory in your field configuration. NEVER do that. And in a similar vein, NEVER put the resolution field on any screen other than a "transistion to a closed type status". (Well, not quite "never", there's a couple of edge cases, but for most Jira systems, it breaks…
-
It's the same answer as before, it's not changed. Jira doesn't have field level security.