Comments
-
Looks right.
-
You'd need to write a new login handler to do that.
-
Boards don't belong to projects. They are a view of a set of data (often that set is a single project, but it doesn't have to be) When you say "combine boards" though, what do you want from the resultant board? Start with a look at their filters - can they be combined simply? (Might be identical, in which case you don't…
-
Cloud has diverged from Server and uses a different numbering scheme. It is "on the latest version" though, generally ahead of Server. I don't know if it has that function actually. Have a look at a permission scheme to see if there is an "advanced admin" option.
-
Yes, you need a password, as you'll need Confluence to log into the database to use it!
-
It hasn't been Greenhopper for years. It's JIRA Software now. JIRA 7.3 gives you another option alongside JIRA Software's "simplified workflow". Project admins can make limited edits to a workflow IF that workflow is not shared with other projects. 7.4 added a specific permission for allowing it because most of the…
-
Ok, can you try indexing the project the issue is in, and then refresh the dashboard?
-
Ok, are you refreshing the dashboard after her change?
-
Epic/Story/Subtask can't be restructured.
-
So it pops up the box and asks her to select an assignee? When she next reports it, can you check that the assignee has not been updated for everyone else as well? Could you read the history of the issue to see if it is recording an assignee change?
-
How are you doing the assignment? And are you refreshing the page that the calendar is on after the assignment?
-
Sorry, can you explain why you are doing this?
-
It can be slow to post sometimes, that's caught me out a couple of times. It also refuses to let me post maybe 1 in 10 answers, with an over-enthusiastic spam filter - do you get any warning pop up at all? If you're using an ad-blocker or javascript filter in your browser, the pop up might be being hidden by them.
-
Disable as many add-ons as you can.
-
Have a look at the bit it's underlined in red! Editors with syntax highlighting and checking are really handy, and much better at spotting small errors than I am!
-
What is the error you get?
-
Have a look through https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html Your VM is unsuitable though - you need a fast *local* disk to put the intex on, SAN attached storage is too slow.
-
I am unable to replicate what you're seeing. I either have to remove project admin rights from my account or share the workflow.
-
That it a really bad way to do it. This file is used when creating an empty JIRA database and for defining what to read out into an xml backup. For an existing JIRA, you would need to manually create the table. You'd then have to implement all the code required to read and write the table, and you would be unsopported by…
-
There's something broken in the file, but it's being lost as you copy and paste. Could you open the file with an xml editor that could check the format for you?
-
No, a user is either active or not. But, take a look at the groups that the two applications use to say "this person can log in". Remove the users from the Confluence groups.
-
Interesting, not one I've seen before. Could you try adding a new dashboard (no need to share it) and see if the error changes?
-
I need you to check Project settings -> Issue type and see if the edit link is there. If it is not, then the workflow is shared with another project
-
Use active objects - the plugins you've seen creating their own tables do it with tables named AO_<plugin key>_name. See https://developer.atlassian.com/docs/atlassian-platform-common-components/active-objects
-
Are these bugs a sub-task type or standard (same level as stories)
-
Yes - give them the workflow you've defined with 6 steps. Give them a board with 6 columns, and other people one with 4 columns, with implementation, verification and team-review in the "in progress" column.
-
So it's starting ok. What does the application log say from the point of start up? What is the server doing as well? Thrashing cpu/memory/disk etc?
-
No, because they're not attributes or fields you set, they're calculated from the issue data. See https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/updating-an-issue-via-the-jira-rest-apis and https://docs.atlassian.com/jira/REST/server/#api/2/issue-editIssue - you're looking for the…
-
Duplicate of https://community.atlassian.com/t5/JIRA-questions/Active-and-Passive-setup-for-JIRA-Software/qaq-p/629247
-
No, that's illegal. You need one licence for each server.