Comments
-
And if you can't download them, you can't read them.
-
Oh, right, sorry. "List all the issues of a project" says you want a list of issues, not the fields that are available. There's nothing in the UI other than the actual screens you use to create or edit, and you can only see those in Admin or by using the screens, which you'd then have to copy manually. A better option is…
-
Go to the "issues" menu and select "search". Search for the issues you want to see, then select "export to csv" from the tools menu.
-
Nor do I. 405 means you don't have permission to post. Are you sure you have the right url, the right user details and that the call you are making is supposed to be a post? And are you sure python sends it over in the right format?
-
Could you tell us which add-on or tool "itrack" is?
-
Jira itself cannot change the custom field type, so there's no API for Script Runner to call to in order to change it.I would add the new field, then script something to read the old one into the newscript something to find where the field was used and add the new one (not replace, the API doesn't support that…
-
The act of reading it in its current format downloads a copy to the client, even if it is just temporary, so no, you can't do that. Your only option is to convert it into a format where they can only view it on screen as an image (and even then, there's nothing to stop them saving the images)
-
I'd start at https://confluence.atlassian.com/servicedeskserver031/linking-issues-802165194.html#Linkingissues-Createanewlinkedissuefromanexistingissueinaservicedeskorbusinessproject
-
JSD has a "create related development issue" function in it that ties the request to the development item better than a simple clone (it has easy automation for "when developer finishes, update request"). It's worth trying that.
-
405 has nothing to do with your script, it happens when you are attempting to pass back a file that does not have the necessary permissions on the server to receive Post information from another script. In other words, your script is asking Jira to do something it does not have permissions to do. Check what you are asking…
-
You only need a 10 user licence, to cover the writers. The 200 customers will be able to see KB articles because they are customers.
-
Cloud trials are for 7 days. I don't know what you mean by "every email ID expires within 30 days"
-
Jira uses a different scheme for identifying issues, and the Trac numbers do not work for it. The only way you will get the numbers to work the same is if you pad the import, such that your Trac system really does have 1, 2, 3, 4, .... 45623
-
Wrong. This community has just started on a mini-project to clean up the tags. There are over 18,000 individual tags. * 70% look useless because they are only used once. Of this block * Around 5% are mistakes, mis-spellings or posting on the wrong subjects * Around 20% are single words * The rest are sentences, because the…
-
Please don't type "exact name", please do what I asked - start typing.
-
You don't. The buttons are named from the transition name. If you want to use the target status name, that's fine, just rename the transitions to the name of the target status.
-
I'm afraid you can't without a bit of code (yet)
-
I am confused. I am not asked for gross/net or anything like it when logging time.
-
If you want more on point 2, here are two horror stories about custom fields: 1) The far too common one: Like many of us, I inherited a Jira system and was told "it's complex, it's slow, it's confusing, we're hiring you to help fix it". There were 40 pairs of "Start date" and "End date" variations. Apart from looking…
-
Sebastian is correct. Off the shelf, Jira focusses on task tracking. Adding Service Desk and/or Software adds layers around managing the tasks in different ways, and to some extent Software does some resourcing stuff (mostly with Scrum or trying to make sure not to many issues are in flight) But there are loads of add-ons…
-
The "status buttons" are the workflow. To "remove" them, change the workflow so that the transitions are not there, or not usable. (Pretty much makes Jira pointless, but I assume you've got reasons)
-
I don't think it would be secret if it's been gathered or kept, but you're looking back 14-16 years to a product that didn't have a huge organisation behind it and they simply may not have the numbers any more. Also, as the Jira licence is "in perpetuity", people who've had it for a year could have continued to use it…
-
Yes, because Core Jira uses the resolution for everything to do with seeing an issue as "done", you should always consider the resolution in your workflow. Strikeouts, created vs resolved gadgets, version reports, everything looks at resolution.
-
Not natively, as it's a security hole to allow sending of mail to people who can't see your issue. There are add-ons which enable you to lower your security like that.
-
Mark them as favourites, they get added to the drop-down. The reason there are two default filters is that they are useful to everyone who is using Jira in a vaguely sensible way, and very helpful for new people, or even old hands like me who can't be bothered to recreate the filter again.
-
It's not "stupid and pedantic", splitting sub-tasks across sprints makes a nonsense of the numbers, is complex to handle, hard for humans to grasp, and in real life, does not work. I'd suggest you have a read through the conversation above properly instead, look at the reasons it does not work, and then look again at what…
-
You paste the new licence in. Atlassian tend to expect you to continue with the trial installation, not create a new instance. But if you've got a separate production, paste the licence key into it, and remove the one on the old system.
-
Ah, I didn't see that. Yes, it limits it to 20 elements. But starting to type the name of the group should limit the list to matching entries. IS that not happening? What do you get?
-
Yup
-
On the pop-up the group picker presents, look to the right, there should be a "show number of groups" drop down. The default value is 20.