Comments
-
You blank it out, not use a word. The rule JIRA uses is simple - if you looked in the database, you'll find the table jiraissue has a resolution column. When this is empty, JIRA displays "unresolved". When it's filled (and it doesn't matter what with), then an issue is struck out, and treated as resolved. If you just…
-
That would suggest that an inexperienced admin has done a really bad thing and added "none" as a resolution. Go to the list of resolutions and check that! (Also check for any other resolutions that are badly named). If it is, then you'll need to fix it, and as fast as possible. If it's not, then we'll need to look at a…
-
No, the new role is independent of other roles, so adding a new one and granting it browse does not affect the others. You can not "deny" access. You have to remove the access that is being granted to the people who you don't want to see it. In other words, remove "any user" from the permission, and add back in the smaller…
-
Ok. So you have "Tests" as an issue type. But that does not explain what your "test cycles" are or how you are storing the results.
-
No, Jira does not have "test cases". You need to explain how you have implemented yout test cases, test cycles and execution results in Jira before we can help you. Are they using the standard functions in Jira (i.e test cases are issue types), or are you using an addon to help you with it (if so, which one)
-
Which test addon are you using (if at all)?
-
I suspect someone has used an invalid coding type to write the name of the issue type in another program and then copied and pasted it into the name in JIRA. As an admin, go to Admin -> Issues -> Issue types, find the issue type and edit its name. I'd blank out the existing text completely and then type it in rather than…
-
No. The domain names are fixed. You can migrate to a new one - see https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html You can also rename your site, but that won't change the url it lives on.
-
Probably a simple filter for "assignee = <user>"
-
<strong><a>progressWorkflowAction</a></strong>(token, issueKey, action id, remote field value array if you need to update fields)
-
You need to create the scripted field, before you can use it.
-
Assuming the scripted field is called "Sprint Count", then the JQL is "Sprint Count" > 1
-
With the script runner, I'd create a scripted field that counts up all the sprints an issue is in. No need to use it on screens, but you will then be able to say "Sprint Count > 1" in JQL
-
If you're stuck, then post all of the memory settings here. Java memory settings are not as simple as just increasing one to make a problem go away.
-
There's a few things that might be wrong here. >JIRA login wrongly reports "Sorry, your username and password are incorrect - please try again. This is quite a subtle use of language, and although it seems clear, it is not, but with good reason. You may well have entered a username and password combination that you think…
-
Indeed. You could also leave the boxes off the screen entirely and put in a transition back to the same status. One for each subtask type that needs doing, which uses the CSOT and then sets the tick-box, and another transition that has conditions like "not allowed if sub tasks are open" and "not allowed if there are no…
-
Ah, now that's clear. You want something that will create one sub-task for each "ticked box". The plugin Dieter points you at will do MOST of the work, most importantly, the harder bit of creating the issues. However, it's not quite what you need. If you add (say) three copies of it, it will create three subtasks every…
-
Exactly, it's all a bit too vague for us to construct a decent answer. I would also have guessed that you wanted something like what @nbhushan has suggested, but we can't assume that from your question or comment (and I've been caught out making assumptions like that before, ending up giving completely inappropriate advice…
-
But what have the fields got to do with the subtasks? A check list is a field, or set of fields. Nothing to do with sub-tasks. Please explain the behaviour you are looking for?
-
I'm not sure the question makes a lot of sense. I understand you want to create sub-tasks, but what has that got to do with fields? A sub-task belongs to an issue, you create them by adding them to issues, they have nothing to do with fields. To expand the questions: Where are you selecting issue fields? What does a…
-
>Let say event X is fired when a custom field for an issue is changed. For the third time, and I'm running out of ways to say it. Events are fired by ISSUE changes. When you change an issue (maybe changing your custom field), you could get event X, Y or Z depending on your configuration. Could we step back from this and…
-
Again, events are fired by ISSUE changes. When you change a field, that's an issue updated or one of the transition events. When you change the ISSUE, events are fired. You need to catch them
-
That will capture all events. You might want to code it to ignore some Events, rather than run code that looks for a change of your field every time, but you don't really have to. As an example, I would consider ignoring issue delete, comment update and delete, and so on. Events where your field cannot change...
-
1. Yes, an event is fired on every occaision a field is changed, but you'll need to trap several 2. No. Events are fired by things that happen to issues, not fields 2 is the whole point of events, they are issue changes. A field could be changed on create issue (from null to something), issue edit, during a transition, and…
-
There doesn't seem to be an "issue" here. The status that an issue can take is determined by the workflow that the issue type is set up to use. That list is set up by you and your administrators (there is an alternative - if you are using "simplified workflows", then the available status is determined by your board, but…
-
In the database, which you should not touch. Propertyentry if you want to read them.
-
Because Atlassian are moving to have "project create" create projects that do not share schemes at all (Screens, permissions etc) Prefixing the new screens and other items with the project code that caused them to be created is a sensible move, as you can see exactly what it is doing at a glance. (My opinion is that this…
-
I thought it might be that one, but it's always worth checking when the question is so vague. There's loads of organisations not in that logo, so I'm curious to know why the poster thinks an obscure one like vitech should be there.
-
Where are you looking at this logo? Why do you think vitech should be in it? (I don't think I've ever heard of them).
-
My very first response to your question explicitly said You should replace it with a "filter results" gadget instead. I'd suggest taking a little more care next time you're reading an answer.