Comments
-
I seem to remember that it's board.getQuery() for a query with IDs, or boardGetNavigatorQuery() for the more human friendly one.
-
If you have one of the scripting add-ons, then yes, a scripted field could easily work out a percentage from time estimated vs logged or remaining. You'd want two fields - one for each issue, and one for parent issues that accumulates the child issue values.
-
Look in your profile (the icon for your avatar at the top right of Jira)
-
That's fine - it is exactly what the "field configuration scheme" is for - telling a project which field configuration to use for each issue type.
-
I can only think of two ways to do this, one involves hacking (can you check your "system information" page for "changed files"?) and the other assumes that when you say "pull story out of sprint" you are changing the underlying status of the issue - is that true?
-
Hard to say as the problem is on the HockeyApp side, but the error message is saying that either you can't log in to Jira because your username/password combination is wrong (can you log in as "admin" with that password in the GUI? I suspect not), or that the user "admin" can't see whatever project it's trying to look for…
-
Also check if you're running this stuff as "root". It should not be run as root, and if you do run it that way, it clobbers all sorts of stuff.
-
There isn't enough of the log here to tell you what is wrong - you need to go further down to find the errors.
-
Create a new, empty database for Confluence on the MySQL server and follow the installation guide at https://confluence.atlassian.com/doc/confluence-installation-guide-135681.html
-
The properties file holds things Bitbucket needs, including the database connection. That's why it thinks you've got a new install,
-
Correct, if you can't see it, then you're not the buyer or named as one of the billing or technical leads. Two routes - one is asking your admins, and the other is to raise a request with Cloud support - they'll privately be able to give you the names within your organisation.
-
It's also very hard in SQL as well. Imagine that you're just looking at a single permission in one project, such as "log work". That line will give you a rule for access, but that access could be * A group (you'll need to read the users out of the groups) * A user * A role (you'll need to read the project header for users…
-
Yes, you can use the database tools to do this. As long as restoration of data will not change the new collation back. However, if the collations are very different, you may find some of your data changes to match. The xml export/import is agnostic of that.
-
The default notifications are for reporter, assignee and all watchers. I'd strongly recommend exactly what @[deleted] and @Joe Pitt said - get your admins to ask the users what they want, and take the axe to the scheme to get it to be more quiet. However, to answer the original question, you need to do two things: 1.…
-
If you've got a commercial licence for Jira, then you're entitled to a "developer licence". You can install your own copy of Jira to play with, and give it the dev licence for your rummaging. Or testing, development, upgrades and even disaster recovery.
-
If you need the functionality of component lead, then you have three options: * Stick with using components, and accept that they are multiple-select. You can't change that on Cloud. * Use a single-select field and buy Cloud add-ons to enable scripting or pre-built post-functions that can implement what you need * Move to…
-
The easiest answer is to have different workflows for the projects and simply use "set field to" post-functions that set the assignee to different people. That can be a bit clunky, especially editing a workflow when someone leaves or changes role. I prefer to use more advanced functions from certain paid add-ons (assign to…
-
The "reimport with default paths" should load the attachments using the system path, with your /data/apps/servwell/attachments being used for it.
-
By default, the Atlassian stack will live entirely in /opt, so the short answer is "use the OS recommended minimum sizes for all the others, and look at your long-term data requirements for the applications to determine /opt".
-
If you need to keep the original, then clone and move the clone. If you don't want the original to stay in the source project, then move it.
-
There's no harm in taking an issue from backlog straight to done without going through a sprint. Think of the cases where you are grooming a backlog and think "hang on, this one is a duplicate/won't do/misunderstanding" - those go to done without any work The most simple trick would be to have a transition that allows you…
-
If by "based on", you mean "make a call using the ID as part of the url", then no, you can't do that with summary. The ID is unique and part of the issue's url, but a summary is a field on an issue and may not be unique, so it can't be used as a unique identifier. You can however run searches over REST, so you can do…
-
Fisheye 4.2 should be ok up to Jira 7.2. 4.3 for 7.3, and 4.4 is compatible with 7.4 and 7.5
-
The user is defined in one of the scripts in <jira install>/bin (it varies between versions, so I can't say which one you have. Probably set-user.sh)
-
That's because you're looking at a 6 year old thread. You can no longer change the attachment path in Jira, it is always <jira home>/attachments. You can still mount different directories there or use symbolic links to place it where-ever you want, but you have to do that with the operating system, not Jira.
-
Talk to your Jira administrators. If you're saying you can't re-open it, then the most likely reason is that you don't have permission or the workflow does not allow it. And your admins have set it up that way.
-
It is a sum of the estimates. Jira is making the total more human readable - most of us grasp "days/hours/minutes", but struggle with blocks of minutes. 480 minutes for example - not at all intuitive (Despite being a familiar standard working day in the West) You can swap this in Admin -> Time Tracking, but generally most…
-
Operators like and and or are for joining clauses, not data, that's why your first two lines don't work. Your second two lines are closer, but have a re-read of the one that "takes" - if you separate the clauses individually, you get "(Issue type = Story) and (Issue type = technical story)". An issue can only be of one…
-
You could, but you should really use the developer licence for this. Under the licence key in your my.atlassian.com account, there's a link for the developer licence.
-
Could you explain what this has to do with Atlassian stuff?