Comments
-
Ping doesn't always work - some of us disable it to make servers less obvious to attackers. If you're still getting a timeout, but you know the lookup is ok, it's a firewall blocking access over that port.
-
Global ranking forces product managers to co-operate (or just look stupid - their choice) Boards don't have to include everything. If a PM doesn't care about a set of issues because it's not their project, don't include them on their boards. Then the global ranking relative to the stuff the do care about is irrelevant, as…
-
Admin rights give you admin. Not "I can do anything", as that's a dreadful permissions model (and really gets in the way when you have even a small system with a modicum of complexity) You need to make yourself a user within that project. Check the permission scheme to see what roles or groups to add yourself to.
-
You can try adding multiple rank fields, but it tends to be a complete disaster, as each field makes a nonsense of the others. It's no real sense to have boards ranked differently as well. If one issue is more important than another, why should it appear differently on different boards?
-
All issues have an "edit" button if you have edit permissions in the project. Changing issue type can be complex. It's a structural thing. But you can do it with a drop-down if you put issue type on the edit screen definition, and make sure the various issue types all use the same field configuration and workflow.
-
When "Software" was "Greenhopper", there was an association, but that's before v6!
-
:-) Shame there's no emoticon for grumpy penguins. A spinner and a timeout usually means the client machine cannot resolve the host, or that if it can, there's no response. Check the host resolves with a ping or nslookup, and then if it does, the firewall rules.
-
I think your memory may be wrong. Rank is a global field, and it ranks every issue against every other issue, irrespective of type, project, board etc.
-
A sprint appearing on another board happens when the sprint might include issues on that board. You will not lose the sprint on the board you are not deleting, it's just a warning that the current board will stop reporting on it.
-
What error do you see? "I can't connect" tells us nothing (for all we know, it might be because there's a grumpy penguin sitting on your keyboard saying "no")
-
Thing is, if you've not configured anything to do with it, Jira won't have any way to trigger doing stuff. I suspect one of your users has done something you don't know about. Start with a look at * Application links * Bamboo configuration Make sure there's nothing there for either of them!
-
Ok, I'm completely lost on what the problem is now. Could you give us a worked example? e.g. from a board with something like "project = X", two quick filters, what happens when you select one, then the other, and then what you really expect it to do differently?
-
You don't need a "template", just fill in the data as laid out in Branden's links. A "template" is only going to be useful for one specific user's needs, which will almost certainly be different to yours.
-
You're drifting off-topic now. Let's concentrate on the first problem instead of wandering on to another one. What happens if you change the board filter to just "project = SSRF". Can your user create the sprint now?
-
Assuming you mean Jira, then no. Custom fields are for issues. The meta-data associated with versions is not issue data, and you can't add to it.
-
I'm not sure what "edit field of a workflow" means. Look at the transition from <not closed> to <closed> - it has a box with tabs such as "post functions", and an edit to select which screen the transition uses. Decide if you want to ask the user about a resolution - if you do, add a screen, if you don't, add the "update…
-
I think you need to track down where all this Bamboo stuff came from. A new, empty Jira I created this week does not do this. When I imported a shedload of data in it by importing, it does not do this. It is now linked to a Bamboo instance with a small handful of new plans created this week, and it does not do this. You're…
-
Same answer.
-
Edit your workflow. Each transition into an "ended" status (generally the green ones) should either * Have a post-function that sets the resolution field * Have a transition screen that has the resolution field on it * Never both, just one of the two Also remember: * To put a "clear resolution" post-function on "re-open"…
-
The general advice you're going to find here is "do it in Jira". Confluence is for free-format documentation and collaboration on blocks of human-facing data. Jira is aligned with discreet tasks, one of which can, of course, be testing. However, Jira is a crap testing management tool on its own. It's an issue tracker, not…
-
That sounds correct to me. It sounds like each quick filter is being "anded" with each. Is that's what is happening?
-
There's no way most of us could have guessed that. It sounds like your best best might be to stop using the add-on!
-
Yes. See https://confluence.atlassian.com/adminjiracloud/creating-issues-and-comments-from-email-779288896.html
-
On Cloud you don't have access to the Jira API, only the REST API, which is a sub-set of everything you have available in the UI. If you can't do it in the UI, you can't do it with the REST API.
-
This sounds like a problem with the repositories and your connection and/or access to them. Sourcetree is just showing you another symptom. You'll need to get the repos or your connection fixed. We can't tell you where to start with that unless you tell us where they are.
-
Jira doesn't have "component versions", so I don't understand what you're doing here. Could you explain?
-
The "stays in the same status as it was originally" is the show-stopper. Transitions are supposed to change status. There's nothing wrong with looping them back to the old status, but Jira doesn't have an "transition that goes back to itself automatically from all status". Your "transition for 8 status" is the only way to…
-
Click on the "insert row beneath" button on the toolbar, after putting the cursor on the right line. There's no keyboard shortcut for this though.
-
Your Excel has been misconfigured to read CSV as SYLK - you need to tell it that this is a CSV file, not SYLK.
-
I thinks Ipsita worked out how to check they had permissions for all projects the board *might* include.