Comments
-
I'm afraid there's no way to do this. One trick I've seen is to have a specific "sprint" issue, one for each sprint, that then allows you to attach sprint stuff to it, along with other data you might need. You could do the same for boards.
-
You don't. Projects contain users, users do not have projects assigned to them. Go to the project, and, as an admin, add the user(s) to the relevant role(s)
-
Links will appear on the issues you've linked from, so that should solve the problem for you. Matching fields in custom fields could be done, but it requires code, and if you have a lot of issues with a particular value, you're going to have performance issues. You shouldn't be trying to do vast numbers of links of either…
-
So you're saying you want to link issues without linking them? Using a custom field instead of a link? Is that right?
-
Ok, I admit that I'm stuck - you're doing everything correctly. I'd want to look in the log to see if there are any errors when the transition is run, but that's clutching at straws. It looks to me like the standard functions won't clear the labels correctly.
-
Ok, that implies that the change of field is being done after JIRA has stored the issue data. Could you have a look at the exact order of all of the post-functions on the transition?
-
Ah, yes, the labels field is an unusual field and I'm not sure the JMWE does quite the right thing when it clears it out (I wrote something like that a while ago, which worked fine for most custom fields, but did much the same as you're seeing here) In this case, I'd try other options to update the field - do you have any…
-
Which add-on are you using to provide the "delete field value" and how is the post-function configured?
-
I'm not sure I'd like that - the point of a forum is that it's a community, and a place to share. Private messages discourage that. But it would be nice to have a way to contact someone to see if they were willing to accept mail off-forum.
-
Changing email content is still a matter of editing templates in the application. ("Code" if you like, albeit non-compiled code). You don't have access to edit the application code, so no, you can't change the content.
-
"safely" downgrade - not really. It is a minor version, so it might be possible to export it, change the version in the data, and re-import it. Or possibly even just flip the version down in the database before connecting 6.4.0 to it. But if you do it, you won't be supported, and the effort might be a lot bigger than…
-
Eh? No idea how you might have got there, that's quite a leap in the wrong direction! All you need to do in your JIRA is separate out the schemes. Let's say you have the default scheme and it's called permissions-A. If you want to make project ABC work differently to project DEF, then you change the schemes for them.…
-
Create a new permission scheme and associate it with the project you want to handle separately to the others.
-
There's generally no need to have a bulk-delete of a custom field. It's not often people delete them, and when they do, it's usually only one or two at a time.
-
I can't think of any way a restoration of xml would do that. Were there any other changes?
-
The error os clear to me - you have to fill in a fix version because it is mandatory for the issue type you are moving the issues to. The greyed out retain option is probably there because you have one or more empty fix versions in the source issues (the field is mandatory, so you can't keep a blank) or you are moving to a…
-
Depends on your database settings. For mysql, try <span class="kwd">SELECT</span><span class="pln"> default_character_set_name </span><span class="kwd">FROM</span><span class="pln"> information_schema</span><span class="pun">.</span><span class="pln">SCHEMATA S </span><span class="kwd">WHERE</span><span class="pln">…
-
That's the way the editor works - the edit screen is a simplified version of the end result.
-
Look for "time tracking" instead - it's an oddity, most other fields are just simple fields, but the time based estimates look like several fields, but are actually just one, named timetracking.
-
Write the story, get people to review it, comment on it, and update it, gather a consensus and then raise it in JIRA for the developers to have a look at.
-
I don't quite understand the requirement, it sounds to me like you want a user-picker that behaves differently on-screen, but I'm not sure. If that is right, then the answer is that you will have to write an add-on that provides a new type of field. You refer to a validator as well. Not sure what it has to do with the new…
-
I think Atlassian are going back over old unanswered questions recently, picking up some really old ones without answers.
-
Someone using your account did. You might want to change the password or check with your colleagues
-
No. Component values are determined by the project. If you need different ones by issue type, then use a custom field with different contexts (multi select list)
-
What does the documentation say to do? Presumably it's "install from the UPM", but then what does it say? Should it add links into the interface?
-
You can't do this - a column is a collection of status and nothing else. The issue type is irrelevant, but you do need to check that the board filter will pull out the issues (project = XX is a perfect one and very simple) For your bugs to appear on the board, you just need to make sure that they are in a status that is…
-
The issues you removed from the sprint. Are they "done"? (Your "unresolved sub-tasks" comment makes me wonder if the parent issues are done)
-
Um, I did know the answer, I gave one route to it because most people tend to use the diagram nowadays. The text route only differs in that you could say in step three "In the text view, click on the status"
-
Ok, the page I gave you has the values you can use, but I'm not aware of a really simple clear guide to getting to the place you use them (other than Christian Czaia's course on the subject) So... * Go to the workflow you want to do this to * Edit it (to get a draft) * In the diagram view, click on the status (let's say…
-
JIRA workflow properties - you can set a flag on a step in a workflow that says "no editing". You can also block comments and other stuff in a similar way. Do editing first though - the reason I say that is that there is an example of it in the default JIRA workflow that you can't delete - look at the properties on the…