Comments
-
All of the OnDemand systems I have access to take me to a simple user and group maintenance system. When you say "go nowhere", what do you actually mean? URL stays the same? Same url, blank screen? Different url? What does the "source" of the page actually say? (Just because it's blank doesn't mean there's no data on it).…
-
No. See https://answers.atlassian.com/questions/10147/can-a-project-or-project-category-have-its-own-priorites
-
JQL is not SQL. It finds issues. It does not say anything about what then do with those issues. Your reporting structure there is not something JQL can do, as all it works with are issues.
-
Sorry, that last one was a bit terse. By "it doesn't matter", I really mean that when you're using an issue tracker and the data doesn't fit what you're reporting, it's fine to take a good guess (or even pick randomly), as the people picking up issues are likely to be able to edit the data to make it more useful to them…
-
Seriously, it doesn't matter.
-
That's why I said to not worry about the precise values. If you really insist on raising this issue against a product that probably isn't going to be maintained, then you can enter whatever seems closest.
-
Sorry, I meant that I'm not sure it's worth entering precise versions data for Answers bugs because the product is unlikely to be maintained in the future.
-
I'm not sure it matters too much. Answers is based on OSQA - Atlassian have taken that and customised it. However, it's going to be migrated to Confluence Questions soon, and I don't think there are any further bug-fixes going into (OSQA) Answers.
-
Pretty much what JIRA was built for, yes. I think you may want to expand on the question?
-
That's not just a "migration between servers", you're doing a massive upgrade as well. Moving from one database to another is generally a doddle if the databases are the same (eg mysqldump > output.dmp, then myslql < output.dmp to load it on another server, then hack the dbconfig file to point at the new one). Your upgrade…
-
Ah, there's a couple of other fixes for the broken issues (although they are variations on "amend your workflows" or "reopen and re-resolve them". Sorry it's too late!
-
First, check that you have not got "resolution" on any screen where you do not want it set to something (it should only be on the view screen, and screens that go into status where you want a resolution set. It must not be put on create, edit or most transition screens) Second, check the workflow for set/clear resolution…
-
Install crowd, visit it in a browser. I'm afraid your question is far too vague to give you a useful answer. You need to explain the rest of your question.
-
Your customised workflow does not contain the "resolve issue screen" on the resolve transition, or a post-function to set the resolution automatically. First, fix the workflow by putting in a screen with resolution on it (only on resolve/close transitions! Never on edit or a transition into "open"!). Or use a post-function…
-
I'd start with a new Space, created from one of the standard blueprints. That will give you a "home" page which you can use as an example - most of the standard ones have sections, panels and examples of macros you can build on
-
Ah, a panel type thing. I'd start with the panel macro, and probably fill it with dynamic macros, like the content-by-label or children (that way you don't have to keep editing the page, you just create the pages you need)
-
What's a "bucket" here? What does that mean?
-
>Create issue screen will refresh Does that mean that when you click create, the screen refreshes to the same create screen? As though you had failed a validation and need to go back and fill in a field correctly? Or do you mean it drops you into the issue view (where the user can incorrectly change the field by clicking…
-
Add-ons are supported by their vendors, however you got them, and whether they are Cloud or Server. Atlassian support can help you with a lot of questions, especially on Cloud, but any use of an add-on means they have to rely on the vendor's help to support it.
-
Add-ons are supported by their vendors, however you got them, and whether they are Cloud or Server. Atlassian support can help you with a lot of questions, especially on Cloud, but any use of an add-on means they have to rely on the vendor's help to support it.
-
Go to global permissions and add the group to the "can use" permission. Then add the group to space permissions with the right permissions for that space
-
One. Your production licence entitles you to a "developer" licence, which is explicitly for licencing dev, test and failover machines, so you should be using that, especially for any DR testing. Atlassian understand the "fun" that can be had with Disaster Recovery, and although you might find the licence agreement has…
-
Because that's the only way you can do this. If you're deleting the feature, there's nowhere for the links to go. If you want to keep the links, you need a copy of the feature to hang them on.
-
Eh? You've said you are deleting the feature. So it doesn't exist.
-
But that's the point - you're removing the feature, so the link between the feature and the story has to be removed.
-
If you delete an issue, then the links have nowhere to hook into, so they have to be removed as well. I think it's behaving correctly here. But I think I may have misunderstood the question - could you explain what you expect to happen to the links if you delete one of the end points?
-
To confirm: * The issues are In Progress * The issues are returned when you search for "status = open" * The issues are not returned when you search for "status = In Progress" * If you re-index them, the searches start working? (A global re-index, or a simple edit of the issues will do this - I usually add a full stop (.)…
-
The done column. Coudl you explain what status you have in the done column?
-
It depends on how the board is set up - is your "done" status mapped into the "done" column? Did you set a resolution on them as well? I don't think you'll need to change the wizard, just map the data differently.
-
There's no difference between trial and full functionality. Could you explain what you mean by "company structure feature"? As there's nothing I'd describe as that in JIRA or Confluence.