Comments
-
Move over to Server, either hosting it yourself or getting a third party to do it (there's lots of providers). The new UI won't be coming to that for a long time, if at all (hopefully, never, or if it does, a version that has been fixed)
-
There are no field types that do this. You could try Behaviours to show/hide the second field based on the content of the first.
-
Try the "add transition" button you mentioned. If you want to be able to get to your new status from any point in the workflow, use a "from anywhere" or "all" transition. Otherwise, you'll want to select a start status. When doing this, make sure you add a transition out of the status (or have at least one other "all"…
-
Start with the notification scheme for the project. You are getting "issue updated", so have a look at that line in the scheme. List out who is supposed to be notified (it could be groups, roles, project lead, assignee etc). You then need to flatten that, looking at a list of every account in the groups, every account in…
-
There's nothing formal on the roadmap. At the Barcelona summit, I asked a few developers and the best I could get was "no chance before the next US Summit". I'm hoping this gives them time to fix the new UI - there are a lot of people who hate it and even I, as an Atlassian fan boy, find it has far too many usability…
-
* Irregularly and frequently - Atlassian release updates when they're ready. They've recently announced a "long term support" policy though, so Server users don't feel like they have to upgrade every 6 weeks. * Manual * Yes * Depends on the size of your system, how you are migrating any add-on data, and what changes you…
-
What does the log (<jira-home>/logs/atlassian-jira.log) say the problem is?
-
Yes, adding a status to a workflow does nothing of itself, you also need to give the users a way to move issues into the status. That means adding transitions.
-
>We created a new row in the table jiraissue ARGH. Never never never do that. Inserting issues via SQL is complex, painful and absolutely requires that your Jira is offline while SQL is being run. For example, did you update all the tables you needed to insert an issue? Unless you can tell me (without searching), which are…
-
What do you mean by "Confluence Chat"?
-
What does the log (<jira-home>/log/atlassian-jira.log) say is wrong at the time of deleting?
-
No, you need to read <jira-home>/log/atlassian-jira.log as Fazila said.
-
Issue is Jira speak for "the entity that represents an individual thing that needs some attention". It is the core object in Jira, the single thing that everything else revolves around. Issues have a "type" (which is seen by us humans as a name), so that they can have different ways to be seen and processed. Story is one…
-
You could reconfigure the Tomcat to run on port 80, but it's better to stick a proxy in front of it.
-
Inline scripts are fine for the odd little thing that you can easily replicate and for developing them, but for proper scripts, I keep the <jira-home>/scripts directory under source control.
-
The table is Bodycontent, but you really do not want to do this. To make sense of the content, you're going to have to write a parser to read and interpret the content into something you can read and analyse properly. If you do this the right way, instead of SQL, it will be far easier - use REST to get the content.
-
This seems like a drunken "stream of consciousness post", which I can't read properly. The best I can do is suggest that you should go down the Service Desk route, simply because it really helps your end-users create really simple requests without needing to know anything beyond how to write text on what they want to do.
-
The use-case you describe is a cascading select, as far as I can see. Could you expand on what I am missing here?
-
Right. That was a vast waste of everyone's time then. Five days before you bother to tell us you are not even looking at Jira while asking questions about Jira. Confluence looks at the saved filter. If you want to see the definition of that filter, go to Jira and look at it.
-
Either: Edit the workflow, adding a "will not do" status to it, with transitions from the right places, and setting the resolution field with a screen or post-function. or Add a "will not do" type resolution to the list and make sure your Admin can transition issues to closed and use that resolution.
-
No. Admin means admin, not "do everything", although an admin certainly can allow someone (including themselves) to do anything. You don't need to mess with global permissions for this one, just make sure you are at least a Jira admin, so you can edit workflows.
-
Log in as an admin, go to the project you want to change this in, and go to the project admin section. Look for the workflow section, descend into it, going down to the workflow that is in use for bugs. Use the edit option, you will find "add status" appears along with all the other editing options.
-
Go to board admin and add all the columns you need. Then add the status to the right columns. Then set the limits. It's all on-screen in front of you, so I'm not sure where you are stuck.
-
The most likely reason is that you have not been given "restrict page" permission in this space. Talk to your space admins to get it.
-
Have you tried adding a cascading select field?
-
Not with javascript, you need to work with the numbers.
-
You have configured your Jira to use a user directory that it can only read, not write. So you can not edit the group from within Jira. Because you have chosen to make it read-only. To remove the user from the group, go to the user directory and do it there.
-
No, you'd need to hack the layout code in the core of Jira
-
Ok, where did you do the installation?
-
It's not. It's calculated from the key.