Comments
-
Ok, so which method do you want to run with?
-
So, Cloud? If so, that sounds like a bug - worth reporting it to https://support.atlassian.com
-
Yes, JIRA doesn't have a "tests" thing built into it, so you will need an add-on. However, there are a lot of options for a testing add-on. Testrail, Test Management for JIRA, Zephyr (Server or inside JIRA), qTest, and and and. You'll need to define what you want from a testing add-on and have a look at all the options in…
-
Whichever you want.
-
You can't do it on Cloud, and for Server versions, you should be doing this with your network, not the server (or not at all, as it's a doddle to bypass)
-
Logo of what? Project or system? And what version are you using?
-
Create an account for them.
-
Could you show us the whole query you are running?
-
The alternative to importing is to restore a database backup and a copy of the system's home directory on to the test server.
-
Do you have any versions set up?
-
The whole point of a board is to represent where your issues are in the process, so the columns are coded to be status containers. Swimlanes are the way to go for this. Although, if you're ok with add-ons, Comala Canvas lets you set up a grid with several options for rows and columns.
-
You have the right idea with the REST API, but the rest of the question is really not answer-able. Cloud won't provide you with "exports". The REST API does allow another system to fetch what it wants, when it wants it. So, the concept "export data" is not goint to work. You need to be thinking in terms of "external system…
-
Go to a sub-task and go to it's standard JIRA view. Click tools menu Click "convert to issue" JIRA will walk you through any questions it has. The least it will ask is "what type?", but there may be more if the configuration is different.
-
I should say that a lot of that is a copy and paste from an old blog that ended up in an admin training course somewhere. I'd encourage you to ask rather than struggle - JIRA is complex for admins (it kind of has to be, so it can be flexible), but there's lots of people here happy to help. The only reason I answer…
-
Those things are not "tabs" (if you look at the bottom of the screen, you'll see tabs - All/Comments/Worklog/History/Activity). I'm also lost on where you're seeing "Categories" - those don't have anything to do with workflow in JIRA. What you are looking at here are "transitions". These are part of the workflow. A…
-
Sorry I couldn't do a lot more, the original question turned out to be conditions, but you've definitely got a different issue here, and as it's likely to be a bug on cloud...
-
Ok, this is something I think they've released recently which has broken some of the javascript. Could you send it over to htts://support.atlassian.com ?
-
Sorry, I misread the bits about the browser. It sounds like there is a problem with the browser/code combination. Are you on Cloud?
-
It's the conditions on the workflow transitions.
-
For the case you describe, considering QA to be part of the sprint is by far the best option. Don't clone or move on, your QA should feed back quickly and enable you to deliver rapidly, as it's part of your sprint. It's not always, there are times when it doesn't work (when QA is completely separated from Dev for example,…
-
No, that's good, if you log in as the "bitbucket" user and see no tables, that's what we want. Next step is to test that that user can create tables, index them, and drop them. Then, we need to start the installation of a clean bitbucket server again.
-
There's no way to do that directly. You'll need to duplicate the board query for each swimlane.
-
Conditions, I know they're there, I tell people about them all the time, and I still look at my own workflows and wonder what I've got wrong. You're not alone!
-
That property really does only affect edit. It must be something else preventing the transitions.
-
Yes, try the tools menu, it has move options.
-
Yes, it depends on the workflow and the board configuration.
-
No, that's showing the correct state of affairs. A board defines the right hand column as done in the sprint. You've got one issue done in that screenshot, and two incomplete, so the completion box is entirely correct. I suspect what you should do is swap the "in review" and "done" columns.
-
Not off the shelf - the "Status Category" is not available to the gadget. You'll need some code to make it available.
-
No. The Status "field" is not doing what you've said here, and it's not a field anyway, it's an indicator of where the issue is in the workflow. You should look instead at the Status Category, which shows you "to do", "in progress" and "done".
-
It's the "output type" that tells JIRA where a field should be put. I understand that the duration field has the flag that says "I'm date related", so JIRA pulls it out into the dates. To move it, I suspect you'll have to raise a request with the SR team to get it changeable.