Comments
-
Some field types have more functions than others. Plain short text for example, is just that - a box for some text. But a select list field has options, and options which can vary by project/issue-type, so it needs more operations to control it. You won't get "access to other operations", because they're simply not there.…
-
I'd put the table on a separate page, then use the include macro to repeat it in as many places that I needed it. One place to edit it, many places to see it.
-
You don't. Permission schemes are associated with projects, and tell the project rules on "who can do what in this project". You can put groups into permission schemes, (e.g. "in this project, the group X can resolve issues"), but it's strongly recommended that you do not do that, and you use roles instead. The use of…
-
You don't. The strikeout of resolved issues is common through Jira and Greenhopper. If you want to remove it, then you need to a) change code in several places and b) educate your users that you are removing information that many find useful I think a better start might be to explain *why* you want to remove this function.…
-
You could attach the video file, but as JIRA is not designed as a file store and they tend to be large, it's not recommended. A better option might be to link to videos stored on proper file storage that's been built for videos.
-
We've all jumped down the wrong bunny hole at times ;-)
-
Um, that only gets part of the requirement (what about the type of user?), and can't handle "Time Spent" anyway.
-
I'd use the script runner to write a "validator" - it should be easy to pick out the current user's group (or role? Roles are better and easier to use than groups) and whether their update includes Time Spent data.
-
JIRA is an issue tracker JIRA Agile is an addon for JIRA that enables Agile functionality such as boards (scrum and Kanban), sprints and sprint planning, reporting associated with Agile and so-on. Note that you don't need licences for Cloud, only Server versions of the software.
-
Yes. But only if JIRA is not running - do not touch it until JIRA is shut down.
-
What do you mean by "close a workflow"? Are you using the "close" transition on an issue? Or editing workflows? What versions of Jira and IE are you using? Does it do it when you use a proper browser like Chrome, Firefox or Safari?
-
Yup, that plugin sprang to mind as soon as my father-in-law said "it's a bit bright". I've seen it used in a few places, although only on monitors and TVs used as monitors so far (not Smart TVs browsing to the pages)
-
We didn't try that. The remote seemed to emulate tabbing between links/buttons and so-on so we could move around, and obviously a "select" behaved like a left-mouse click. Not convinced the order was as friendly as it could have been, but it was still usable.
-
Actually, yes, I was tinkering with this the other day. My father-in-law's nice new Smart TV displays Jira with Greenhopper very nicely over the internet, although we ran into two minor problems: 1. Jira tends to be quite white or pale, whereas TVs are usually positioned and adjusted for watching colour rich programmes.…
-
Ok, then we can rule out using a single issue type. So, we need to know what you've customised and where (removing the issue type selection is a bit of a pain, and very user-unfriendly, we should be fixing your code, not reducing functionality elsewhere)
-
Ok, but that still means you will only be able to create one issue type? If that's correct, then you can just change your issue type scheme so that there is only one issue type available and the issuetype field won't be able to change. I suspect that's still not what you really want though - you really want to be debugging…
-
You can't "disable issue type field". The issue type is mandatory, Jira cannot work without it. If you disable it, you won't be able to create ANY issues, which would make your Jira useless. I think you need to explain the requirement in more detail, as it's not clear what you really mean.
-
Yes, and you've almost answered it yourself. You mention that your transitions set different flags - you can use those to detect/infer what transition was used. You could easily use another custom field to store it as well.
-
Absolutely, although it's better presented in the history tab. I'm not sure what the best angle for your needs are, so I'll explain how I'd do it for a single issue, just to explain the relationship. You need to look at three tables. Jiraissue contains the issue, most importantly, the unique and immutable issue-id. You can…
-
It's in the issue history tab - you need to look for each change of status (The jira suite utilities is just summarising information it's pulling from there) There's no way of knowing what "button was clicked" though - there are many ways of triggering a transition and how they are triggered is completely irrelevant, it's…
-
That's only cooler if you really need to do complex data manipulation during the merge. Bulk edit will ask the essential questions and deal with all synchonisations etc. Scripting is more work, and a lot slower.
-
Not really - moving issues from the first project to the other is pretty much the best option. With bulk-edit of course (someone I know tried to do it one issue at a time! Fine for a handful, but he had hundreds to do...)
-
I was referring to the whole of JIRA. If you have not changed the version of JIRA, then there are two other possibilities1) You have a custom REST add-on which you have changed2) Your external code that is calling REST has changed
-
Er, your parsing results have not changed. What it actually looks like is you've upgraded JIRA from 4.2 - before 4.2, select options were strings, after 4.2, they changed to options. But Cloud is kept on the latest version at all times, and that's presented select lists as options over REST for many years. So I think the…
-
Make sure that your project has at least one version defined. A Kanban board will create one when you use the "release" button, or your project admins can add one in the UI or by trying to set one on an issue.
-
You do not. Jira won't return all issues because you could overload it. JQL is not the problem here, that really does return all the issues, it's the macro itself and the code in Jira that serves up the results. I suspect you could code an alternative interface which a macro could use instead, but you'll be running the…
-
"Read data" is too vague a specification to give you more than really generalised guidance. Why are you reading? What do you want from it? There may be plugins, you might have to write something, no way of knowing until you explain roughly what you want.
-
Use the REST api
-
No, there isn't - hence the answer of "database hacks or scripting/code"
-
Ah, yes, but one of the things that all good JIRA admins do is remove all rights for users to delete issues. It's a baseline recommendation - it should NOT be easy to delete. I'm glad you have caught up with the logic now.