Comments
-
Hi Jean, I am not familiar with the behavior you mentioned - "done" column is limited to card modified the last two weeks. Is this a TMP or CMP? In TMP there is a rule to age done issues after 14d such that they are hidden from the board. I would not expect them to reappear if the old issue is modified as I would assume…
-
So you indicate “feedback requested" field? I thought we were talking about A status of “feedback“? Assuming we are talking about a status of feedback, what was returned when you used that JQL above? Did you get an error or did you get results that you weren’t expecting? Also, you might want a condition that says status…
-
No I mean use Done as your only done category status and leverage Resolution for the variants of Done: done, cancelled, won’t do, cannot reproduce, etc. while there are scenarios where I use more than one done category status they are rare.
-
Couple thoughts…. * include Status on card layout * consider not having multiple done category statuses. Rather use the resolution to indicate cancelled. This is what I do most of the time.
-
In CMP and traditional boards if you have multiple statuses mapped to a single column then when you drag an issue into the column you will see dotted lined boxes for each status and you can drop them into the appropriate one
-
Have you inspected the link and compared to one that is working? Have you tried additional Browsers ?
-
Also you might reference this article to get you started into the world of advance searching - https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-searching-in-jira-cloud/
-
In the basic search screen to the right you will see a link that says advanced search. If you click that it will convert your basic search into advance JQL. You could then add that snippet of JQL that I provided. If you click on that link and copy the contents of that JQL box into a reply here I could modify for you then…
-
This is not possible OOTB. You would need to look at a different email handler addon.
-
Charles, Based on your list of reports I am guessing that you are on a TMP project. At the moment that is the limit of reports that exist for those project types. CMP projects have quite a few more reports. You might investigate the documentation and see if any of those reports are meaningful to the point of wanting to…
-
There is an open suggestion for this - As a user, I want to have the ability to customize required fields
-
Yes that is the correct format. in your case regarding the warning I wonder if the auto-renewal is the culprit? specifically the “-“.
-
I would recommend you post the answer here that solves your problem. The benefit of the community is sharing solutions so that future searchers might find this answer useful.
-
I suspect that a member will see all necessary fields. Certainly easy enough to try just take a single user that is a viewer now make them a member and see if they can view all the necessary fields
-
Ok. If this user is a customer and not a Jira account then you can edit the name. To do this, click on the cog icon in the upper right hand corner. Select user management then Jira service management in the sidebar. Find the users name (James Dean) and click on edit full name. If however this user has an Atlassian account…
-
No I don’t have any experience with this or have discussed with colleagues what they might be using. Good thing is you can always try these things out and turn them off if they don’t work for you.
-
Well I don’t use TMP I suspect this is by design and cannot be changed unless you change the user to a member instead of a viewer. Here is a article around permissions by user type - TMP Permissions I suspect this directly influences field access.
-
Yep one of the downsides of a SAAS based solution.
-
People watching! You see all sorts of people there.
-
The current answer remains.
-
I would refer you to this document on TMP permissions members are granted sprint permissions.
-
I guess your account type is free maybe? The only thing I can think of is to create a new instance under a new site administrator and perform a migration.
-
There isn’t a solution for that out of the box. You’d have to look at some other mail handler solution such as JETI or JEMH.
-
That specific customization is not part of cloud. You can read about customizing your portal here. Be sure to explore the sidebar articles https://support.atlassian.com/jira-service-management-cloud/docs/add-announcements-to-your-portal-or-help-center-in-team-managed/
-
Not sure I follow. Are you wanting to create a project in your instance and then have the customer import into their instance?
-
Yes they changed - https://community.atlassian.com/t5/Jira-articles/Priority-icons-are-more-accessible/ba-p/1732935 AFAIK you can’t “revert”. You could consider creating and setting up your own. As a site admin - administration - issues - priorities , edit each priority and set URL to where your icons reside.
-
You might consider creating a custom field (OldKey) and run an automation to copy the issue key into that field then ensure the new project retains that custom field. I have not done this but should work.
-
No. The old issue key will be gone.
-
Yep that is the “move” approach. If you follow that process then yes you should preserve all issues as part of the move. Note that your issue keys will be different but all tickets should exist.
-
So that link is to the server version of documentation not cloud. Your tags in this post seems to indicate that you were on cloud. Can you clarify? Assuming you’re on cloud and assuming that you are a site admin or have permission to add a banner here’s how you would do that: on the help center click on customize tab on…