Comments
-
If editing the database, you must - stop jira, get a backup, prove it works by restoring it and testing it on a dev/test system, run your SQL, start Jira, reindex and then I recommend the integrity checker too, just in case. Having said that, hacking a handful of create-dates is not going to be a huge risk, as it's a…
-
We can't really tell you how to implement your own processes. What you're writing out here is a good definition of a workflow which sounds like it will work well for you. You should go ahead and build the workflow like that and try it out with your users!
-
Same way you deactivated them. It's a simple flag on that page.
-
Ahm I see, it's the details on the boards for you. Again, most people like that view, and the complaints you see about it are about it not being customisable enough, not about the idea. If you want the full view, you can use right-click -> open in new window on the issue key on the card. I'd be tempted to say that the link…
-
Actually, they added the detail view because users told them it was a better starting point than the list view. For myself, I can't judge it because I've been using it for too long, but a lot of the people I work with prefer it as the start point for new users. Anyway, yes, I think an add-on could swap or even disable it…
-
You can't disable it without killing off the entire issue navigator. For the coding, you will need to get the JIRA source code, find the part that implements the two views and remove either the button to swap it or the entire view, recompile it and apply it (rendering your system unsupported and a nightmare to upgrade)…
-
Most of us find it useful. But I suspect everyone wants JIRA to remember whether we were using list or detail view (so if your users never use it, it'll remember list view for them) and that's what rjakes' issue has been raised for - it's not persisting for a lot of people.
-
Thanks! /me clicks on vote
-
Mmm, well, I haven't needed to switch so I don't know if it's just affecting you or all users. Forgetting the setting might be a "on upgrade/reboot" thing at a guess. Have you raised it with https://support.atlassian.com ? They can confirm if it's a bug, a design decision or something you're doing.
-
I personally am 50/50 about it, I don't prefer one over the other as a starting view. Most of my users (and presumably, the people the Atlassian UX people have interviewed) prefer it this way.
-
It's remembering what you last did, which is how most people work. It doesn't work for me personally, and it sounds like you see the same as me. But it works for the overwhelming majority of other users, so it's a good way to do it.
-
The answer I've given is probably all you're going to get. There is no option to turn it off without hacking core code, and it would be a significant downgrade and cause you lots of issues when upgrading, as well as people asking where it's gone when they need it. You've listed a set of problems with the view that you…
-
You can't, without hacking the core code in Jira. I can't see how this is causing support issues for you, it's a simple matter of telling your users where to click to swap between views (and frankly, detail view is often useful to many users and turning it off would be a downgrade). People who have used Jira elsewhere, or…
-
No, it's a lot more flexible than that - you usually devolve permissions to a project level, which understand permissions on a set of "if then" situations. For example, if you have a permission scheme that says "team lead can assign" and leaves developers out, that answers your question. But you can set up a different…
-
You said that already Please, could you type the query I gave you? The autocomplete should help you fill in Bob (and Jane later).
-
What does the auto-complete do when you start typing Bob?
-
My quotes were there to indicate the sentence as the distinct part of the answer, not to be pasted in direct. Try it without the quotes, but type it, so that it auto-completes the user names for it.
-
"z in (x,y)" is an or-type compound, it's asking the question "is Z in (x or y)?" I think you need to try "inspector = Bob and inspector = Jane"
-
>I suspect I'm not adding much to... That's adding a lot, it's really useful.
-
To keep it really simple, yes! A new issue type of Incident is the most simple, and probably the most clear way to do this. If you go with an incident issue type, you'll be able to give it different fields and workflows to the other issue types as well, if you want. And it will fully support Service Desk in the future too.
-
I think you need to define "synchronise" for the first point. On the second, I don't think there's a plugin around to do that, so you'll need to write your own. In both cases, I'd strongly recommend taking the code you have for 3.11 and upgrading it for your current version of Jira.
-
The only difference between an evaluation licence and a full licence is that the system effectively stops working when an evaluation expires. All the functionality you get with a full licence is there in a trial.
-
That could only happen if you've run the installer and overwritten your existing JIRA installation. The installer will have upgraded it all.
-
JIRA does not have an automatic update function, so I'm not sure what you're doing there. Your versions are unclear - there is no JIRA Software 6.4 really - do you mean JIRA 6.4 with the Agile add-on installed? If so, you can install Service Desk as an add-on via the UPM.
-
No. A component is a way of showing that an issue is related to a specific part (or several parts) of the project. A backlog is a list of issues you need to deal with.
-
Why should GET be idempotent?
-
No. The reporter field is a field that points at a user's account. If the user doesn't have an account, there's nothing for it to point to. The best you can do is add another (text) field to capture the users information when they don't have an account.
-
Start with https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens - the easiest way to get to the right schemes is to look at the project configuration
-
You'll need to check two things * That the "timetracking" field is on the screens for the sub-task issue types * That the fields are not hidden in the field configuration
-
You can use it any way you want. It's there, in the application, listening for incoming connections. Doesn't matter how you do those connections, as long as they're in a format it understands