Comments
-
No. In fact, it was recently removed as an option on Cloud. See https://confluence.atlassian.com/jirakb/jira-miscellaneous-workflow-extensions-jmwe-removal-from-jira-cloud-815262011.html for details (and how you can get to it's functions)
-
No, Confluence's task management functions are a simple and convenient task list. They're not an issue tracker, they're very very very basic and don't do anything more than that.
-
Yes, you can.
-
Er, 2.5 years old, but also behaving exactly as expected. Nope, not buggy.
-
Ah, yes, it's a trap many fall into, and it's not brilliantly clear in the docs either. Jira sees the resolution field as <null> or <something from a list of strings>. It displays <null> as "unresolved". But if you add "unresolved" as an option, it sees them as resolved, because the field now has something in it. I'd…
-
Oops, sorry, missed the "xml" part of your comment. An export won't help you that much - there is a simple "set field to ..." function built into Jira you can search for, and when that is configured to change the resolution, yes, you'll be able to spot it. But then you also need to spot transition screens with resolution…
-
Also remove it from transition screens, or your users will set it inadvertently.
-
There is no fault, but there's two glaring ways this can happen: 1. Indexing problems. Could you try re-indexing and see if that makes it consistent? 2. You may have had an inexperienced admin add a resolution of "unresolved", which neatly messes the whole thing up - check the list of resolutions, and remove it if they…
-
Sorry, this does not join up as a question. Domains are domains, I don't know what you mean as "verified". You'll need to talk to your domain provider to change those settings. SAML has nothing to do with your domain settings, and you've flagged this question as JIRA Cloud, which simply does not support SAML, so that's no…
-
Ah, no, you'd need to hack the code providing the summary screen to add that filter to your display.
-
Same here - "components list showing done tasks" makes a lot of sense, but is somehow slightly too vague to be telling us what the problem is.
-
Your only option for Cloud is three filters - filter 1, filter 2 and then filter 3 includes both 1 and 2 (join with an "or" is the easiest choice)If you were not on Cloud, there's an add-on which provides a function "is in filter (x)", but you'd still need to use the "or" in filter 3
-
One minor point - the 200,000 limit was a recommendation for Jira 3. Although Atlassian haven't really announced another number, Jira 4 and 5 can happily handle a lot more, and you can get into millions if you're willing to put some effort in on decent hardware and proper application tuning.
-
I suspect "archive" is similar to what I've been asked to look into loads of times - a whole project, no updates going on at all, should be read-only, but you still need to search for it.
-
You've neatly ruled out all of the current options in your question. I've had discussions with Atlassian people about archiving in the past, and I know they are actively working on something that will help you with it. But I'm afraid I don't have any timescales or details that I know are accurate enough to be worth sharing.
-
Each user can turn off "auto watch" in their profile. You can also change it in the global user defaults.
-
No screenshots :-( Could you check exactly what the workflow scheme says (i.e. what workflows it uses for what issue types) and then check that it is definitely associated with the project?
-
It's in the same place as "change workflow scheme". When you go to the project administration screen, you can select a new workflow scheme, issue type screen scheme, field configuration scheme, issue type scheme, notification scheme, permission scheme etc.
-
Could you not simply point Jira at the mailbox and import them that way? I know the processing in Jira off-the-shelf is basic, but it's good enough for many people. If you need something a bit more advanced, it's well worth checking out https://studio.plugins.atlassian.com/wiki/display/JEMH/JIRA+Extendable+Mail+Handler…
-
Your full license entitles you to a developer license. I'd use that to get the old system running again - as long as you don't use it as a real service, that's fine.
-
You can't use those admin settings on Cloud Confluence, there's no custom html allowed.
-
I think it's a minor issue, but one that increased in severity when Epic and Story became special issue types in the Agile plugin. Atlassian have stated they won't fix it though (sorry, I don't have my bookmarks to hand), on the grounds that it's not a serious problem and not many of us voted for it.
-
Not really. A user in a project can either create issues (of any type) or they can not. You can play some tricks with fields to block them, or other javascript tricks to try to supress it in a browser (javascript is easy to bypass and won't work if they use REST etc).
-
Yes, that delete the access.
-
You try telling a tax man "some people gave us money for our software, but we've deleted all record of who they were and what they bought". Yes, that's clever.
-
Actually, that sounds reasonable to me. You'd want to retain basic contact details, otherwise your auditors would be questioning where the money came from. I know of at least one arrest in a company I worked for because someone deleted audit data. They should be able to mark it inactive in some way though.
-
Select any of them.
-
Contact Atlassian support.
-
Yup - see https://www.atlassian.com/software/jira/download-eap NEVER use one of these in production. There is no guarantee that the data will be usable once it has been imported (and it takes weeks to unpick it when someone ignores that advice) Always work on a copy of data and assume you are going to throw it away after…
-
p.s. the filtering stuff I am thinking of is what @Davin Studer is explaining a lot better than me!