Comments
-
It will work for sub-tasks on standard issues though - they take the security level of their parent.
-
That won't work. Issue visibility is done at a project level on the most part, so a user must be able to see the project that their issue is in. Then you can restrict the issues further by setting a security level. But they're user based, nothing to do with components. And you'll need to set the level on all issues you…
-
I think this one really does need to go to OnDemand support - if there's no un-install in your account, I've got a feeling that you can't remove it completely without at least a restart of JIra, which needs Support...
-
Some addons are locked in place in OnDemand, you need to remove the addon via your OnDemand management account - if you go that way and it still persists, you'll need to raise this with OnDemand support.
-
Mmm, sorry, that used to work, but now it needs the 2016 to be a word on its own. It won't find partial words, so 20/3/2016 won't be found.
-
You've answered your own question - a field that is text cannot have a range searcher, it's not got data that can support it. It's a bit like asking "are those colours between two and four?". The data does not know it might be searchable. "create date" ~ 2016 will work, but it's going to pick up the 20th January and so-on.
-
There's nothing wrong with your query. What you are missing is that JQL is for finding issues, NOT reporting on them. The list you are getting is right. You are then displaying the list of results in a function that reads the details and displays them (such as the issue navigator). That function is built to render the…
-
I've not worked with a validator that does that, so I don't have anything to point you at. I do know it's possible, because I did it for a client once (a very old version of Jira and a very clunky method, but it did work)
-
The standard validators are quite limited in my opinion, and the first thing I usually do with a new Jira site is install the Jira Suite Utilities which adds a number of validators (and other stuff). It's free and can be used OnDemand. If that doesn't do what you need, check the marketplace for other plugins, there's quite…
-
Indeed - conditions are there to stop a user starting a transition, whereas validators are there to prevent bad data being logged - they block the transition after the user has entered data. However, in the case of Resolution, you don't actually need anything. If you put the resolution field on a transition screen, it gets…
-
Not without making some code changes. The line-by-line layout of Jira is quite simple and hard-coded in the files that draw the custom field area. Some people move the fields around with javascript, although I believe that's become harder in Jira 5+ I've not seen a plugin that makes this any easier I'm afraid.
-
JQL is for finding issues, it has nothing to say about what to display about them. So, the first part of your question is easy - issuetype in (Epic, Story) The second part about displaying them simply goes back to what you are displaying the filter in. If it's the issue navigator, you can tell it to show you the summaries…
-
Not really - Jira is for issues, Confluence for writing pages, and the calendars hang off those. I'm not sure what you imagine you could do differently.
-
I'm not sure what the question is. You start paying more if you store more than 25Gb.
-
Sort of. See https://confluence.atlassian.com/display/AOD/OnDemand+Storage+Policy
-
You could do either issue types or workflow schemes first, it doesn't matter which. I'd generally advise doing issue types first though - workflow migrations can be complex, and there's no actual point in doing them if you're going to end up dumping an issue type and hence it's workflow. From your screenshot and comments,…
-
I'm sorry, I don't understand the question now. What do you mean "only wants to migrate to the default workflow"? Surely you've set up the new workflow scheme to use new-wf? Or have you got several workflows in the new scheme? (It only offers you status in the new workflow because you can't move outside the target…
-
I think it's because the "new" status are not really "new". Imagine you have two simple workflows called old-wf and new-wf. Let's say they are really simple and look like this: old-wf: Open -> In Progress -> Closed new-wf: New -> In Progress -> Done If you migrate issues from old-wf to new-wf, Jira will ask you to tell it…
-
No, you can run it on a Cloud development service as well - as explained in the doc you linked to. But that's not a server edition of JIRA, it's a Cloud install.
-
This developer mode is for Cloud, not Server.
-
Er, if they are genuinely inactive, then they should not be emailing Jira. You need to stop that, then make them inactive. Easy trick though - create a "null" email address on your mailserver and set the inactive accounts to use that email address. Then Jira won't be able to match emails to the accounts and will reject…
-
Mmm, the request doesn't make sense to me, the project summaries are the sane place to land a project link. On the technical side, you can't link to a dashboard page, because they are designed by users, so there's no fixed target to aim at. The project has no way of knowing that "user X has a random dashboard Y that he…
-
There's not enough information to begin to answer this. Could you explain - what link? Where is it, what does it do?
-
I can confirm what you've found if it helps. Moving issues from one type to another is very complex because all the configuration is hung off project/issue type, and that's why you have to go through several steps to ensure data integrity. As you've found, no-one has written a publically available post-function or process…
-
Could you confirm that you are on Cloud? Cloud does not have "Agile", it's all JIRA Software, so you're making me suspect you have a server version, with a different licence scheme.
-
The pictures you are attaching are a fixed size. There are no word attachments. The pictures are not big enough. It is irrelevant what you open them with. I suspect you are dealing with this via email, which won't show you the results of what you are posting - please try it in a browser, and right-click and download/view…
-
Could you stop using Word to "attach" stuff? Take a screen shot as a simple image and upload that. Word is useless as an image editor, whatever you are doing is crippling the images and is not needed anyway.
-
Could you stop using Word to "attach" stuff? Take a screen shot as a simple image and upload that. Word is useless as an image editor.
-
Useful to know it's browser specific. That implies that IE is failing to handle some standards-compliant CSS somewhere, which is a good lead on what it might be. (The obvious fix is to stop using IE as it's not a lot of use beyond giving people an easy way to download a proper browser, but I know a lot of people are stuck…
-
That's an improvement - I can see the problem. But it's still too small to see exactly what is going on. I can see that the highlighted line is shifted right (it wasn't in the earlier pictures, but we'll work with this one as it's clear). But I still cannot make out the column headings. That could be very important here…