Comments
-
No, sorry, that's me thinking through the implications. "Closed issues should not be ranked" is not quite the same as "I don't want to rank a closed issue". However, it ends up the same when you go through the process. The fact you want to strip rank off the issues means the same thing whenever you look at the data - a…
-
Well, sort of - you're still seeing rank as a number, rather than a relation. That's not what it's for, it's really not supposed to be a number. The numeric values should generally be ignored because they're not for humans. Even if you forced Jira to clear the value, it still wouldn't have a simple 1/2/3 counter value for…
-
Ranks are relative, not absolute, and the absolute number is not actually important if you're using it right - that is, you are ignoring the closed issues and using rank to order issues. You could fiddle around removing a rank, but what's the point? The highest ranked issue is the open issue with the lowest value for rank.…
-
By title, I think you mean "summary" in JIRA-speak? Unless you have a custom field called "title"? Either way, you are nearly there already - the right to edit fields is controlled by the edit permission, and it sounds like you do not have it (no edit button) Talk to the project administrators about being added to a role…
-
Go to the field in the list of custom fields and select the "edit" option. You need to select a "searcher" in there (and re-index all the projects using the field to make it work)
-
It's possible to import project data or everything into OnDemand. But, OnDemand has some limitations, and there are some things you can do in Download that you cannot in OnDemand, so if you've taken advantage of any of those features, you may lose access to them. You won't have any problems with upgrading - OnDemand is…
-
The whole point of a Kanban board's columns is that they represent a status (or set of status) within your process. The status must change if you move columns, by the very definition of what it is for! It's nonsense to say a column change doesn't mean a change of status. I'm actually a bit stuck on suggesting a solution,…
-
You'll be glad to hear all the other scheme stuff is more simple. Screens are the only ones with three layers at the moment, and I like this table (it's not naming all the schemes, its a sample) Project levelIssue levelotherIssue type screen schemescreen schemesfour screensField config schemefield config Permissions Issue…
-
Correct, completely. Except I left one bit out. A screen scheme also has a fourth screen, which is "default". This is set to the screen you want to use if you don't fill in one of the other three. It's just a way of shortening the list though. An example here would be * Default: Bug edit screen * Create: Bug create screen…
-
p.s. the schemes are not organisational, they tell JIRA what fields to show to the user when the user clicks create, edit or view on an issue.
-
You need one screen scheme for each type of issue you wish to behave differently. I usually keep the screens separate, but you can share them. For example, you could have screens as follows: Bug create Bug Edit Incident Create Incident Edit View all (which contains all the fields from both issue types) Then your screen…
-
Screens are a collection of fields that you want to show to a user at some point. A screen scheme collects them together, defining a screen for Create, another for Edit and a third for View. This is quite handy because it means you can do things with different fields. For example, you can have a "Create bug" screen that…
-
Yes, one of the many reasons for NOT trying to be clever with javascript - it usually breaks on every upgrade.I'm not sure you can do this as simply as you could in Jira 5.2 - I'd strongly suggest starting again from scratch. Although I really don't see any use for wanting to remove the columns either - my instinct would…
-
There's not enough information here. Answers is not on version 6.3 and doesn't have configure columns - do you really mean JIRA? And what do you mean by "script"? And why? If you are talking about JIRA, and you're trying to stop offering fields to users, then you have a nightmare of a job becasue your script is going to…
-
Start with a look at the application logs under <JIRA home>/logs
-
There's something in the header data that can't be rendered correctly as html - perhaps a "special" character? Do you have a working subscription email to compare it with, so you can see what should be there instead of that block of error?
-
Code. Jira's implementation of versions simply doesn't have any support for adding fields to versions. You'll need to think about data storage (I'd use active objects) and how to hack the screens to allow maintenance and display of the data.
-
Ah, I see, you've been very generous with the permissions. There's no advanced navigation in the assignee field because there's simply no way to accommodate all the different arbitrary rules various users might have for how they want to narrow it down. There are a couple of tricks though... Christian has already given you…
-
>Unfortunately JIRA doesn't let you pick assignable users by groups/roles to which they belong Yes it does. You limit the assignee permission to the roles you are interested in and then only put the relevant users and groups in that role in the project.
-
:-)Now that's established, the short answer is "yes". I've used JIRA to track H&S issues, quality and so-on. Although we see its use mostly in software, it does get adopted for all sorts of things because the core really is an "issue tracker" and it doesn't actually matter if your issues are around faulty software, faulty…
-
Possibly, but google returns my acronym first. That's why they should always be explained.
-
You might want to explain what you mean by QEHS - my memory drags up the Queen Elizabeth High School...
-
I've never seen Jira do that, it's one email per change. As Dieter says, if you've got 5 users to email, all with the same email address, you'll get 5 emails. But you'd get 5 emails irrespective of the number of changes made. The only thing I can think of is a batch of tweaked code in your install, or a listener doing it -…
-
That doesn't sound right to me - all the Jira installs I've used send one email per change. An issue update can affect 1 field or 30 but each user to be notified gets one single email saying "the issue has been changed". Have I misunderstood the question?
-
Yes. And very frequently.
-
That's a very good point - from the technical side, you're divorcing your data into two independent parts - Jira and excel, you won't be able to use the stuff in excel, report on it, or search for it easily. On the human side, the data in excel won't be useful - many of them won't bother to fill it in, and complain about…
-
See https://confluence.atlassian.com/display/JIRA/Defining+a+Screen and look for the section on "configuring a screen's fields and tabs"
-
<grin> It's a good point - Andy has invested a lot of effort in JEMH and it's well worth it if you want to do anything in the slightest bit clever with email in Jira. If you don't want to invest in it, then you will need to write your own handler, and I wouldn't expect Andy to help you.
-
I was just typing a suggestion to take a look at JEMH :-)
-
What do you mean? What customer signature? Or, even, what's a customer? What signature are you seeing? Where is it happening and where is it coming from?