Comments
-
This is a good starting point (and links to a lot more) https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-14
-
To get them crossed out, you have to make the workflow set a value in the resolution field on the transition to done. That needs a screen with the resolution on it, or a post-function to set it automatically (that's what the tick box in the original question does)
-
>workflows, forms, list views, dashboards, custom fields, All core parts of Jira admin. >custom naming of entities such as Story or Sprint You can use separate entities for this (e.g. imagine fields called "start date" and "date of start", although I'd recommend sharing as much as possible, to avoid "fielditis" and other…
-
You could put the link in the field description, but it would be independent of the selection. If that's not working for you, then you'll need some code. The Behaviours part of the ScriptRunner App can do this sort of thing, but you can also hack in some javascript (not recommended though)
-
Matthew Stublefield? He's caught me out on a couple of odd intonations, but to be fair, I tend to say things like "Lurry" when trying to say "Lorry" and "cheese log" instead of "wood louse" - all down to where I grew up. The one I find odd when I hear it nowadays is Jira when it is pronounced "Gyre-a" instead of "Jeera"
-
I have, I'm just not going to repeat the arguments already given above, as you have chosen not to listen. That's fine, you've got one belief, I have another. No I do not work for Atlassian. I've worked in several places, including ones that have software where "admin can do everything off-the-shelf", and seen just how much…
-
Run a filter for "watcher = currentUser()", save it, and use it in a "filter results" gadget. Or use a "watching" gadget in the dashboard. Either way, this is only going to list the first 50 results at most - too many makes it unusable, but you can still click through to the filter.
-
I think you've completely missed all of what I've said. I've already answered all of those points you've made, but I can see you're just not understanding it. I think we'll have to agree to differ. Especially as it's not going to change.
-
Ok. >>At what point do you decide to switch to a different security model? >At the point you're ready to go live. But then you've tested against something you are not implementing. So you haven't tested it properly. >When you're setting up a brand new windows domain, do you need to grant the enterprise admin rights to…
-
It's a proven fact that if you don't start well with Jira, you make a mess. At what point do you decide to switch from a (broken) open security to one that makes sense in the long run? What's the benefit from starting out with one scheme and switching later? Thinking down the road is exactly what you need to do, and…
-
It's a poor security model, and it falls over hideously at scale. Admin rights should give you admin rights, and project rights should be separate from them. If they're not, an admin can't do their job when trying to set other people's permissions, and can easily be blinded by the sheer volume of data they simply don't…
-
Are the bugs in the same project? Some of this behaviour could be being caused by you not having "resolve issue" permission, but that's a project level thing, so it would affect bugs in the same project.
-
Have a look at the "issue type screen scheme" for the projects and issue types, I think they are different. Specifically, in DTI, I think you'll find the screen set for issue "edit" actions does not have the assignee on it, whereas the one for ANX does. A quick way to check this - go back into both issues, and click the…
-
Hmm, that's correct then. Does the field work when you use the "preview" in the scripting screen?
-
There is no way to do this. A dashboard is a dashboard, there's no nesting.
-
It's not a bug, Jira is designed to ask the user to select a type. Not base it on other fields.
-
You'll need to ask the administrators of the Jira you are using.
-
So, what do you mean by "auto update"? The Jira you are looking at went through the setup because it was pointed at an empty database. Until you can work out where your old Jira was, and explain what an "auto update" is, there's not a lot we can do to help explain what has happened.
-
The Set Resolution option only applies in simplified workflows, and appears when defining the board columns. For other workflows, you need to do the resolution by hand - place either screens with resolutions, or "set resolution" post-functions on the transitions into "closed" and "clear resolution" post-functions on…
-
By "online", do you mean Atlassian Cloud, or just a server version someone runs in the Cloud? If you have other similar systems that are behaving, then yes, it's something to do with your account, but the only way to get the field behaviour you describe is to inject javascript that breaks the field in your browser.
-
A default Cloud Jira may already have the app you need. Go have a look at the list of available validators in your workflows (when you edit a work flow, it goes into a "draft" mode which means you are not actually making any change that affects anything. You can discard the draft later)
-
Clearing the cache is not good enough in most cases, so I hope your changes are limited to the places where it is good enough (i.e. not issue or project data)
-
The "mandatory" flag in the field configuration makes a field mandatory throughout the lifecycle of the issue. What you need to do is check it on resolving the issue. This is not a function of screen or field configuration, it is done in the workflow. Edit the workflow and look for the "resolve" transition. If you click on…
-
So you can log in with one browser (which one?), but not Internet explorer?
-
At first, that sounds like someone changed your permissions, but the "scroll" problem suggests something else. Could you try a different browser?
-
How are you representing "test cases" and "defects" in your Jira system?
-
Definitely worth asking. I'm now certain I must have hacked my sources list on the box I was looking at, possibly not for that reason (my actual database server is not Ubuntu)
-
There is no excel export any more (unless you are on server and set a flag in a properties report. And for future readers, past 7.9, that function may go away in any release) You have to use the CSV export instead - I don't think I've found a spreadsheet that cannot read CSV well enough to become a native spreadsheet.
-
What exactly are you returning in the scripted field? If it's the wrong type of object, then in some cases it will display in issues but can't be indexed and hence won't appear in the navigator etc.
-
Have a read of the link Timothy gave, it covers what you can do.