Comments
-
Could you explain the problems they have with the correct technical approach given by Peter? Any other approach is technically going to be a lot harder, so you really should be trying something along the lines Peter has given you.
-
I still think this is an issue with the client's logic, and bodging the software is not the right thing to do. Note that Peter's suggestion is the right approach, despite my opinion that you're doing the wrong thing, whether you do it manually or in code. If you think it through, you'll realise that there's a potential for…
-
It's the wrong thing to do, but yes, with some coding or hard work, you can corrupt the updated date on your issues. Please see the link I gave - it's the same question really, except that with versions, you can write a listener to do it, without having to bodge things into the core of Jira.
-
The version changed. The issues did not change. The updated date records the last change to the issue, so it's not going to change when you change version data. This is almost identical to the question about components over at…
-
See https://confluence.atlassian.com/display/CLOUDKB/Changing+the+Cloud+Instance+URL+Address+or+Migrating+to+a+New+Cloud+Instance
-
Argh, yes, I'm terribly sorry, you'll need a 4.x to go through.
-
I'd bit the bullet and force the upgrade of the whole system. Anything else will be making vast amounts of work for you.
-
Export from 3.6.2 (everything), create a temporary 5.1.7 instance, import the data into that, export it, and then import into production 5.1.7
-
That's at http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission
-
Ah. Then the answer is "no". You'd need customised plugins to do this. For your situation, I'd actually do one of two things 1) Use the "reporter browse" permission - when used in "browse permission", it does exactly "a customer can only see those issues they raised themselves" , but it's not suitable when "customer" means…
-
... and the rest of the question means?
-
I'm afraid the question doesn't make any sense to me. Could you explain differently? I understand that you want to select an issue type, but what does "filer (filter?) custom select list values" mean? You want a different set of options available for a select list based on the issue type? If that is a good guess on the…
-
I could have sworn there was a licence link in version 3's admin menu. Otherwise there was no way to add users to it Anyway, you should still be able to see the numbers licenced in the system info screen - I don't know why you have blank and missing fields in there. More to the point, you should also be able to see the…
-
No, look at the licence screen in admin.
-
No, not the footer, look at the licence screen.
-
What about the other two places?
-
That's not right, JIRA 3 shows you all of those fields and the numbers of users in the system info page (I'm looking at one now!) You could also try user admin -> users - I think that shows you "you have X users, of which Y are counting towards your licence". But I'm not sure what version that was implemented in. Also, the…
-
What does the rest of the screen say about the licence numbers?
-
Although the licence model changes in JIRA 7, the actual use of licences does not change a lot. You still buy a licence for a certain tier of users and apply it by going into Admin -> licences. A licence for JIRA 3 will work for all later versions of JIRA too, including JIRA 7 Core. If you have a JIRA Agile licence, you…
-
You'll need a plugin to do this. There's a rather neat "scripting plugin" from Jamie Echlin, which is generalised and powerful, and also a couple that are more specific will make "child inherit parent's version" ("Misc workflow extensions" springs to mind) Start at https://plugins.atlassian.com/plugin/home
-
No, it doesn't really have an offline component. I tend to write pages up in a text editor and paste them in next time I'm online, or do basic word processed docs and use the word import. Some people have implemented "page create by email" type tricks as well (so emails upload next time you connect and generate pages) You…
-
I suspect that could be a bit like my "did stuff to the disk with another operating system", but I'm not going to pretend I'm any form of Unix expert and claim that's the explanation! Anyway, if you've changed permissions, could you check what you see with three different users? The owner you want to use, root, and some…
-
Oooh, pretty. The ?------- usually means "I, the operating system, either can't read the permissions, or I can, but I'm not going to tell you for some reason". Last time I saw that, it was because I'd created the file system on another computer, with VMS, and later pulled the drive and whacked it in a Linux box. I was able…
-
Yes, and we've had questions in the past that are about setting it up to handle garment size requirements. I've seen it used in several places for the generalised "issue tracking" and "task management" purposes. Specifically, an oil refinery site used it for tracking maintenance tasks, a publisher for the process of…
-
Depends entirely on your workflow. If it has a transition from Closed to In Progress, you can use that.
-
Hmm. I don't think you can. You've ruled out "dummy user with changing ownership" and "changing ownership between individual humans". You've got to do one or the other. This isn't even a Jira question really, it's about process. Iissue X needs to be owned by Y, where Y can be anyone, but only one person at a time. You…
-
Assuming the "user accounts" is a far-reaching job like "merge two companies accounts together" or "implement user accounts across all our applications"
-
An epic is a big chunk of work made up of many parts (stories), a component is something you put on a story or sub-task to show that it relates to a part of your project.
-
Ok, that's the right way to use them. Both of your reports can be done by creating and saving a filter for the issues you want to track and use it in some dashboard gadgets - they can slice up your data by component, epic or whatever. Agile doesn't have a lot to say about this, it's more about the planning and…
-
No, they are absolutely NOT "different ways to tag an issue". You've misunderstood what he's saying. For example: * A component belongs to a project. An Epic can be linked across many projects. ... * Component is stored as a field on an issue. An Epic is an issue in its own right and has to have issues linked to it. ... *…