Comments
-
I suspect we might want to see the definitions of both queries in full. It can be important where and how a clause is added to a query. (If not, then re-indexing is the next step)
-
I can't see the difference between your queries or how you are entering them, it just says "and labels in xxx" twice.
-
Actually, you can't do this the way you're thinking. You've already noted that a condition will prevent/allow a transition to show on the basis of *existing* data - that is, what is on the issue before the user goes into the view screen. That solves your problem for existing data - define two transitions with opposing…
-
I'm afraid REST doesn't expose that (yet).
-
I think the audit-log will capture updates made by users (Note that filters themselves don't just change randomly - your humans have to trigger updates, although this could be done by users in a number of places. Unless there's an add-on written to do it)
-
It's storing the project ID for some reason, I'm not sure why, but if you use or edit the filter behind it, it will save it.
-
This can happen if you change a variable that a filter uses. In this case, if your filter says "project = project-name" and someone renames the project, the filter may resort to using the project ID instead.
-
That's correct. If you mark a field mandatory in Jira, it is mandatory on creation, and must remain populated throughout it's lifecycle. You either need to put the field on the create screen, or make it optional. The usual approach is to make it optional, and then add a "validator" to the "resolve" transition, one that…
-
It's an old trick I learned from JIRA version <mumble> - JIRA thinks in "options" for a number of fields - radio button, check box, select, multi-select and cascading select. Also might be handy to know that the code for radio-button and select list varies only in the GUI (same pairing for check-box and multi-select)
-
It's an "option" - you need to use the text next to the tick. e.g. for field Animal, with Cat, Dog and Penguin as possible ticked options, you want to use Dog to check if Dog is selected
-
You can't. Anonymous really does mean that you've not identified the user. Assuming you have a "contact name", you then need to do some form of pattern matching against your user database - you'll need to decide how best to do that and then write something to implement it (bearing in mind whatever you write cannot be…
-
The log files are kept in the running data directory, the installation directory is probably the wrong default place for them. You can, of course, place them anywhere you like. I tend to go the other way and put the server logs (tomcat) in the data directory as well. What you've done in your hosts file is aliased the old…
-
Do you have "create issue" rights in that project? If you do, and you still don't have the option to convert sub-tasks to issues, then you'll need to ask your administrators to revert whatever it is they have done to remove it.
-
There will be a "convert sub-task to issue" option in the tools menu on the issue view (along with log work, attach, etc)
-
>how are we notified of major releases You need to subscribe to the rss and blog feeds, but they won't really tell you a huge amount about the Cloud releases >and is there an option to not take the new release? No. Cloud is kept on the latest release that Atlassian feel is ready. >Also is there a way to preview the new…
-
I don't understand what you are saying there. I can guess, but I may be wrong - do you mean that you have changed the "create issue" screen, so that the fields for creating an issue have changed? If you just wanted to change the assignee during a transition, you should have created a new screen with just assignee on it,…
-
Same as you asked before - see https://answers.atlassian.com/questions/44352272
-
Your imports are incorrect in the script. Could you explain what you're doing in the script and why you're trying to import something that doesn't exist?
-
I scribbled an answer the other day over at How can I determine the hardware spec requirementswhich covers what I'd say here.
-
That's often the case, and it's why I tend to start with the project config - it at least starts with the right schemes!
-
Issue types can have different "create" and "edit" screens, and you can also limit or hide fields from issue types. (There's a third possibility, but that only applies to custom fields, so I won't mention it here) You need to check that * The sub-task issue type "create" screen has the Description on it (Look at the…
-
Ok, but there's no detail about how you'd import it here, or what the format is. I think you need to check the documentation to find out what "it wants access to the server" means.
-
Ok, well, there's still two issues here "pull in content" - I have a strong feeling that Dita2Wiki simply won't output anything Confluence will understand. I don't know the tool, but unless it specifically says "I can produce dhtml and I'm compatible with Confluence", then I have doubts. "It wants access to the server".…
-
Depends on what you are intending to do with it. Confluence has it's own storage format, so there's probably no direct converstion you can do (most wiki's have their own formats - old versions of Confluence used wiki markup, but it was a different makup to MediaWiki, MoinMoin and the rest. Later versions of Confluence use…
-
Bear in mind that it may go away, as it's a Lab experiment (it probably won't, but don't rely on it while it's a Lab)
-
Yes, and none of that includes "adding an extra step that was explicitly dropped from Kanban because it didn't fit the Core Practices"
-
That's not what Kanban is for, so it's not been coded for.
-
1) Then you don't need to mess with the columns at all.2) Ah, right, that's completely different from what you asked. You could still use a scrum board to do that and just not use the board view.
-
Sorry, I phrased that incorrectly. Kanban's backlog is the first column on the board, it's not that it doesn't exist, it's just there so you can work on it. You're moving away from doing Kanban "properly", so it's not supporting you. Not that this is a bad thing, Kanban is often over-simplified for the real world.If you…
-
You don't have to switch to another board. Just create a new Scrum board and change the filter to be the same as the one for the Kanban board. People can work in either board and jump between them if they want, it's all the same underlying data Kanban doesn't have the concept of a backlog, so you won't quite get what you…