Comments
-
Make sure you create the field with a numeric searcher and a number template, then you should be able to just use return issue.getComponentObjects().size() ; as the script (Untested, and from memory, but I think it works)
-
Ah, I have a trick for that one. If you have the script runner addon, or can write an addon, you can write a new derived field (field with data built from other data on an issue). If that field is a simple number field of "component_count", then you can filter for "Component = myComponent and component_count = 1"
-
Mmm, that's a pretty obscure query - it's not often people would ask for "only that component". Why are things with that component AND other components not important? Surely if component X is breaking system Y, you want the people who own it to fix it for Y as well as X? Also, you say "... and X and y and z..." is acting…
-
Well, that was easy. The add-on is not compatible with 7.1, so it won't work. Not sure why you bothered trying the uploads. Have you tried the built-in user picker? Which has group and role selection in it?
-
There's all sorts of questions or routes to diagnosing this one, but let's start with one that can rule out a lot of them. What version of JIRA are you using?
-
Go to the board configuration and use the estimate setting - you should find you can change it to any numeric field in the system, including Story points.
-
Ugh. Well, you'll need all the tables with "permissions" in the name. Then the CWD tables if you're using Jira's internal users for users and their groups. Jiraissue obviously. roles, I'm not actually sure about. https://developer.atlassian.com/display/JIRADEV/Database+Schemashould help you find the rest
-
That can get very complex - you'll need to duplicate all the processes in Jira that handle the visibility of an issue by user. For the most simple system, you'll need to look up the user's groups, then their roles in each project, then the permission schemes for each and every project and then you'll at least be able to…
-
Ah, I see. It does come across that way. But, it's valid for both - there's no difference in the way you'd use Cloud REST and Server REST.
-
Which API? What documentation are you looking at?
-
I'm not sure what you're looking for there. The database docs start at https://confluence.atlassian.com/adminjiraserver071/connecting-jira-applications-to-a-database-802592175.html but they don't go into a lot of detail because it's simply not that important to most of us running it - select the one of the supported four…
-
JIRA 7 doesn't use HSQL any more, they've moved on to H2 instead. However, it's still effectively file based and not suitable for production use. Given a free choice of database back-end, PostGreSQL is first on the list (Atlassian develop against it and use it on Cloud) with MySQL in second place, Oracle third and MS-SQL…
-
Ah, yes. I misunderstood. Docs, no, but deprecated, definitely not, same as Jira.
-
REST Deprecated? I'm not at all sure where you could find anything saying that! It's completely the opposite story - REST is the way forward for Atlassian stuff See https://docs.atlassian.com/jira/REST/latest/ (Oh, unless you meant SOAP? - not really developed in Jira 4, deprecated in Jira 5, gone in Jira 7)
-
Um, start by clicking service desk in the menu? If it's not there, then you need to install it...For setting up users and so-on, start with https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions Service Desk does change the way that works for Service Desk projects, but you need to understand the basics…
-
Are you still using Service Desk 1? Customers in Service Desk 1 are all JIRA users. So you need to add them as such
-
Ah, yes, the off-the-shelf ones are rather sparse. I'd add the "JIRA Suite Utilities" add-on and try again. It's well supported, works on Cloud and Server, and is free. I don't generally use JIRA without it!
-
I'm afraid you are misunderstanding this. Again, screens are not relevant here. Look at the validators on the transition (in edit mode)
-
The field configuration has nothing to do with the screens. If you make a field mandatory in the field configuration, it has to be filled in on creation of the issue, and throughout the lifecycle of the issue. To make a field mandatory on a transition, you have to add a "validator" that can check the field is filled on the…
-
Screens and field configurations are separate things. I think you're asking about popping up a screen when your users close an issue, so I'll deal with that one, and then you can tell me I've misunderstood It is simple, but you've looked in the wrong place. Having the "close" screen is the correct starting point, but you…
-
No, there's nothing in Jira that provides many fields from one list, except the versions fields. You'll need to find or write a plugin to provide that. I'm afraid the only ones I've seen are very much like versions though - they have dedicated and specific purposes, which makes them less functional as generalised fields.
-
I'm afraid you'd need a bit of code to provide that, and you can't install code on OnDemand.
-
Useful info. Thing is, I'm getting increasingly convinced you're using Jira Agile, not plain Jira. Everything you're seeing is consistent with being in Agile, clicking "create", going through the creation process, and then creating an issue which does not match the filter you've got on that board. Not the "quick filter",…
-
OK, good. What about "browse"? Also, to rule it out, do you have an issue security scheme on the project?
-
That usually happens when you've given yourself "create" rights but not "browse" in the project. However, the fact you can then see it later implies there is something odd going on. First, can you tell us where you are doing the "create" from? Plain Jira? Service Desk? An Agile board? Second, could you tell us what you…
-
Upgrade it to 6.4 first, following the docs at https://confluence.atlassian.com/jira064/upgrading-jira-720411839.html Then go from 6.4 to 7.latest following https://confluence.atlassian.com/migration/jira-7
-
Centos is Linux, and hence yes, it's supported To be a bit more clear, Centos is a Linux distribution, of which there are now thousands. I wouldn't be surprised if Atlassian were to go into a bit more detail and refuse to support the more obscure ones. (Heck, I've made my own distribution, I wouldn't expect them to support…
-
You can't (yet). See https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy
-
Your REST url is wrong. My fault, Sorry, I should have pointed you at https://docs.atlassian.com/jira/REST/latest/- it's got the url guide and a list of the functions if you want to get more clever (like checking issue assignee or something)
-
I'd use REST to try to fetch the issue (it'll work in 5 and 6, so you can do it now and not worry about the upgrade). If it succeds, all is good, if it fails, issue is not there (or, can't be seen)