Comments
-
assume you are in one of those roles for Modify Reporter?
-
this is not possible in JSD cloud. you could consider a completely different portal solution, e.g. Refined. Check marketplace if interested.
-
what shows under Customers for this project? what shows under project settings > people? something odd here... other projects ok?
-
you can't restrict the done column to a number but can age issues off after x-days of being done. for that just change your board's filter to exclude resolved issues older than 5 days for example ... AND resolveddate >= startofday(-5d)
-
do you mean a jql in a search or within the automation? TBH, i have not implemented so can't give you precise instructions. I do expect you can do this w/o needed a field to compare within automation. should be easy enough to try it out.
-
so are you saying you can select the customer during the create but not after? that is quite odd if so. the fact that you don't see any customers in the drop down makes me think there are no customer associated w/ the project. I don't get the anonymous user name is that an artifact of setting customer permissions to…
-
one thought.... you could use Confluence to potential achieve the numbering scheme and underlying link in Jira issues.
-
no idea TBH. I haven't seen anything like that but I certainly am no expert on all-things-marketplace. however, your desired numbering methodology seems to be counter to Jira's fundamental implementation.
-
i think you can use Automation for this. Example of getting the difference between dates {{issue.customfield_10015.diff(issue.customfield_10016).minutes}} Documentation - https://support.atlassian.com/jira-software-cloud/docs/use-smart-values-to-manipulate-and-format-dates/#calculating-the-difference-between-two-dates
-
Screens are not associated to boards. You can create a screen for a specific issue tight. Each screen can display specific custom fields.
-
So you either need to set the reporter to the Manager and ensure the Request type is also set or you can add the manager as a request participant. If the former is used then the manager would see the issues listed in their reported issue if the later they would be under the Anyone reported.
-
not like you illustrate. You might consider different projects for each area so you will have unique numbering but personally I would use components for each area under a single project per product.
-
Your original post was unclear about wanting to add custom fields to details area (as posted in reply to Steven). This is not possible. Beyond ordering the fields on the Screen.
-
Google is you friend here - https://www.atlassian.com/software/confluence/download-archives
-
@giulia.perelli , I believe the issue has been corrected please check and verify. Apparently the answer was somehow marked as spam incorrectly which happens from time to time.
-
Archives - https://www.atlassian.com/software/jira/download-archives but EOL versions are not available.
-
No idea TBH. You might go to JAC and perform a search for an existing issue on this and vote/watch. I would do so but oddly there is a bug when trying to search for “text” when there is more that one word in the text string. It will work on desktop. Try this link and edit the text search…
-
Maybe share some screenshots exhibiting your issue?
-
I have not played with this myself but wonder if some of the “Related content” posts to the right on this page might give the answer or clue?
-
Correct there is no gadget or solution to display done issue in a backlog screen with versions and epics. I was simply offering a solution that would allow you to show done issues in a list or other manner. I am unaware of any such add-on that would provide what you’re looking for either. However that does not mean one…
-
Is the epic in question associated with a Next-gen project? Epic link is only valid in Classic projects (currently).
-
@giulia.perelli , I have reported to Atlassian Community team to investigate.
-
Possibly the instance is not fully setup. If it continues (say 2hr) reach out to Atlassian Support.
-
Jira is designed to have a single assignee for accountability purposes among other reasons. What I suggest is the following. Leave the issue unassigned. Create a custom field of type select drop down with team names. Assign th issues to the team and the on call person would claim the issue by assigning to themselves.
-
If you have different issue types then you can apply different screen and with different screens you can display different fields. So if the boards will have different issuetypes then you can achieve your goal.
-
Migrate is the correct path. What did not work for you when you did that? A Jira user can be a customer of a JSD project and a user of a software project with fill access.
-
To reiterate, custom fields are associated with issues and not with boards specifically. So for example, if you have issue A and that issue is displayed on multiple boards and that issue has custom fields 1,2,3,4 configured to display on the issue detail screen then they will display n that screen regardless of where you…
-
Hi Lindsay, welcome to the Community. So fields are associated to issues and issue screens not Boards. Now you can change what is displayed on the cards in a board or the detailed issue view that is displayed in the side bar when clicking on a card in a board. Can you add more detail on your specific goal?
-
So you should be able to give the client a jira user account and ensure they are not in any groups or roles that might be used in project permissions. Then in the single NG project give them project access. What have you specifically attempted?
-
To be honest I’m not absolutely sure because I haven’t used server in many years now. With that said that is exactly how we used to do it and we had a team of maybe about 5000 users.