Comments
-
No, it's the opposite. Jira considers sub-tasks to be issues in the same way as their parents, barring the sub-task part (which can be simplified down to "they must have a parent issue"). The expand option in the REST API works the same for sub-tasks, because they're still issues in their own right.
-
Tequila... it makes me happy. (hic) I can't believe @Jack Brickey is twice @Meg Holbrook 's claimed age. (I think she's 27, and I'm still pretty sure Jack is still under twice that). Happy Birthday Meg!
-
JQL is for getting a list of issues that match a question. It's up to the reporting or display of these to compile any output you need from it.
-
You can get email support from Atlassian, but all it does is update the requests you raise in the Service Desk at https://support.atlassian.com/contact/#/ Three agents is a "starter" licence which does not entitle you to any support, hence the redirect to the community. We're not support, but we do have a lot of exerience…
-
Ok, great, that's a message that one of your admins has created, and (almost certainly) put in a transition "validator". You need an admin to edit the workflow and change the validator so that it includes the status you want to move from as a valid option.
-
I think you're missing the point again. Could you explain how you think it's ok that I could change your name on your system to whatever I wanted, just because I've decided you have access to my system? Anyway, on the bright side, you won't be able to reset the passwords, log on and change things. The passwords also belong…
-
Then you need to swap to an authentication system where you own the accounts rather than the users. Or come up with a reason for Atlassian to change it, bearing in mind this use case: * I am an admin on a Cloud system. * You are a user on this system * You are a user on your own Cloud system (for which I have no rights) *…
-
To add a subtask, you need: The project to have sub-tasks (the "issue type scheme" includes at least one sub-task type) Your account has "create issue" permission in the permission scheme If both of those are true and you can't create them, then there is something else (script of complex config) set up by your…
-
You will need to contact https://support.atlassian.com/contact to get started on this. We're end-users who have no access to your repositories.
-
If background re-indexing has that much of an effect on your server, you should be looking at the Data Centre option. Also, if it is because of config changes, you should really be running a full re-index to capture all change. In fact, a full re-index may fix the problem you are having (unlikely, but it could) But going…
-
There are a number of ways to "access" the aggregates, but it depends on where you want to "access" them. In the context of an issue view, the issue navigator, reports and dashboard gadgets, they are available as fields. So you just use them as such. The next thing we'll need is to know is what context you are trying to…
-
"db.manager" means "whatever tool it is you would normally use to directly access the database to run SQL queries on it". I would also seriously question why you are re-indexing every week - that, plus the fact you are getting errors smacks of something very wrong that you should be fixing instead of running regular…
-
There is no "synchronisation" to be done here. There is no field that contains the work-logged on sub-tasks. You need to get your plugin to work with the aggregate "fields" (which are not true fields, but calculations)
-
As I said, they don't have configurations, they take their settings from your project.
-
Without Timepro giving you any route to do this with an API or imports, there's very little you can do. Your only three options are really: * Manual duplication * The human route - push back on "this isn't going to change". Point out to Timepro and the people saying it that they are wasting your time and money. Be brutal…
-
Only the user and administrators should have access to change other people's passwords. So you must be asking to prevent one admin from changing another admin's password? That would mean admins would be unable to do their job, and potentially leave you totally locked out. So you can't (and shouldn't be able to) do it.
-
What type of board is it? If you created the board but have no "configure" option, then I would guess it is a "Business" board, which don't have configurations, their setup is a direct read of your project config.
-
My food tastes vary a lot, and I'm rubbish at building a meal where the courses complement each other, so I'll just go over the courses. * A starter of Mr Falafal's finest (Just outside Shepherd's Bush tube) * 1847's "fish and chips", but just the fish part * The "chips" the Old Vicarage in Witherslack used to do to go…
-
Hey, you sass that hoopy @Scott Theus ? There's a frood who really knows where his towel is.
-
You are right, it is shortsighted and a very bad thing to do to your customers. However, this problem is entirely on the Intertec/Timepro side. Jira has interfaces to allow other systems to read and write time-tracking information. It's even more of a failing that they cannot accept even basic imports. I am afraid we can't…
-
Yes. The log says: This could be because: - Your database isn't running - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.) - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.) You have checked the first one, but I…
-
That is what Alexey is asking. Your question was "I need to know elements of Jira". "Elements" is not a word we see used in Jira. It is not like priority, resolution, status, field, screen etc - when you say "elements", we do not know what you mean. So, Alexey is asking you to explain your understanding of "elements". My…
-
That's a very generic error, taken out of context. There should be more of it on-screen, but if that really is all you have, you will need to look at the Jira logs in <jira-home>/logs - probably the atlassian-jira.log file.
-
Yep, if one or more projects had been allowed "browse project: Group (anyone)", then you would see a "projects" dropdown after "Dashboards" in the top bar.
-
So you go to a filter, edit it, run it to ensure it is valid, and click "save". I am not sure there's a way to make that easier. I would however agree that greying out the "save" button without explicitly telling you that the filter is invalid is not right for most users.
-
Before you raise the issue, have you tried the "permission helper"?
-
There is no "trial" installer. You install Jira and apply a licence of the type you need - evaluation (trial) or production are the obvious types. (Academic, Open Source, and Developer are variations on those) If your trial goes well, you're expected to replace the trial licence with a production one - this seamlessly…
-
I have two that are tattooed on my brain somewhere:
-
I am sorry to be blunt, but your conclusion is completely wrong. When a user visits Jira, they are offered the option to log in. If they do (which requires them to have an account), then Jira knows who they are, and hence they are not anonymous. If they do not log in, then Jira does not know them and hence treats them as…
-
The way to get a unique record with JQL is to filter it down to just the one single unique issue you want to see. The result in JQL is a list of issues that already gives you "unique records only" - each issue returned is unique. I suspect I am missing something here, as it sounds like you are looking for a single result…