Comments
-
getLead is deprecated and will go away in a later version. It's just warning you that you should not use it. Try .getProjectLead instead
-
Look at the permission scheme - this is a set of rules about who can do what. Combine that with a look at the users in the project. A common problem is that the defaults for Jira are "access for anyone who can log in", and that's not helpful for a lot of us. What you need to do is look at the permission scheme to see who…
-
You should get in touch with their admins and let them know that they have misconfigured their system.
-
Yes, although it's not done by type, you have to choose the columns you want to download.
-
Ok, I'm lost then, as it's working fine for me.
-
https://confluence.atlassian.com/jiracoreserver070/getting-started-with-jira-core-777015811.html is a good starting point See https://www.atlassian.com/partners/search?name=&page=1&expertise=Training for training providers
-
Your only option is to migrate to Server, which won't be getting the new experience for a long while (hopefully only after Atlassian fix it so it works or abandon it). The new ui is now mandatory for Cloud
-
Go to the filter that the subscription comes from (it's linked in the mail) and look at the top, next to the title, there is "details" which will tell you about any subscriptions
-
Same answer - choose the columns you want in the export and export it to CSV - you should have seen the "CSV (current fields)" right next to the "CSV (all fields)" option you've used before.
-
That is correct, yes. In an ideal world, you don't change a stories points during a sprint (nor do you add or remove stories in the sprint). In real life, these do happen and Jira reflects it as scope change - the idea of the sprint is you say "we commit to doing X", so changes to stuff in flight changes your committment.…
-
You'll need to take that up with the administrators of your Jira3 system. We're a community of end-users who have no knowledge of your systems, let alone access!
-
Start at https://confluence.atlassian.com/get-started-with-jira-software
-
I think you're missing the point - most of us do not have that one set up where it happens to work ok. I did not say you could use mentions in places other than fields, just that I can use them from outside the context of a project, making the permission a nonsense, as well as inconsistent in behaviour for users. A user…
-
Have you just done a direct connection without going through an upgrade? That could explain why it has not worked. Jira will have tried to upgrade the data, but this approach is not right, and it has probably damaged the data. You should revert to the backup you took before your did this, install Jira 6.4 and make sure it…
-
You can stay on 5.2.5 if you want, but it is no longer supported and you get more functions if you upgrade. If you skim the upgrade docs, you will eventually find the recommended route is to upgrade to 6.1, then 6.4, then 7.0 and 7.8 finally. If your data is simple and you have no add-ons, you may be able to go from 5.2.5…
-
Create a filter for the issues you want to report on, and then use it in dashboard gadgets that do the counting for you. You have not really defined how you are storing most of those data points, so I don't know if or how we could combine them. But as a guess that "closed" and "carried forward" are status in the workflow,…
-
Yes, you are mistaken, and it would look stupid to a user as well if you did it by project - why can't I use @mention in one place and I can in another?
-
No, that's nonsense because most of the time you're not in a project so you could have different rights at the same time. If you need to stop users seeing each other, remove groups from the global "browse users" permission.
-
It works for me. But I've just noticed your postings are not consistently naming the property and neither of the usages are correct. Are you using opsbar-sequence? Not opsbar_sequence or ops_bar_sequence
-
Probably simply to fix the permissions. If someone cannot see a project, then they do not have "browse project" permission for that project. You may have "checked all the permissions", but I'm afraid you have missed one. Check that the user is logging in as who you think they are as well as going over the permissions again.
-
Those are html element ids, and useless to you in terms of remote API code. You need to use the custom field id as Kyle says. For cascading selects, you need to set the top level and then use child for the second half: {"value": "Top level value", child: {"value":"IPG Big Data"}}
-
The :1 is not part of a custom field ID, it's wrong. Remove it and try again with a valid id.
-
You don't need a jira administrators group specifically with that name, but you do need one or more groups to be administrators. It makes sense to have groups clearly named for this, so I'd usually re-add "jira administrators" for use here if I found a system without one. Go to Admin -> Global permissions, and look at the…
-
There is no "field" for this. There is a toggle on the estimates panel in the parent issue that tells the system to include the sub-task time estimates in the display.
-
To edit workflow, you need to either: * Be a Jira or System administrator * Be a board administrator and have had Jira or System administrator "simplify" your workflow * Be a project administrator, on Jira Server 7.6 or above, with the workflow being used only by your project
-
It depends entirely on how you are flagging a project as "closed". Jira does not implement a concept like project status. You'll need to describe how you are deciding a project is closed, then we can help you get to it over the REST API.
-
See https://confluence.atlassian.com/get-started-with-jira-software
-
Not directly from the issue navigator, you have to go to the issue view (or edit)
-
Nope, there are other tables involved here.