Project X Tickets
Analisa Wisdom
In this case, my team is working in another project together with another team. Otherwise, we just support partly. By our project we create a meta board to have an overview of the whole activities, including our actions in other projects.
When I set a filter, which set up views from tickets of another project, my board will appear in their projects, not our. When I create a new board with more projects, I see all the tickets of other projects. But we just need them partly (our component, our team or our tags).
You can make these filters quite complex, although I would recommend that you don't try to be too clever - you should aim for board filters that you can easily explain to the team using the board. "It's listing all the issues in our projects, plus some from other projects where they need our help (and have somehow indicated that on the issue)".
You should also consider the component lists - remember that components are project artifacts - the component you have as xxx needs to be a component from project B as you're saying "And project B" in there.
I do not think this can be done - the "belongs to a project" thing is derived from the issue selection in the filter, so if you say "project B and component = x", you're explicitly excluding project A, so the board won't appear as linked to A any more.
That assumes "closed" is a status that issues land in after they've been through an ended sprint, or is not mapped on to the board at all. If it's a Kanban board with a sub-filter, you could do "and fixversion is not empty" as Kanban boards, by default, drop issues with a fixversion set!
I would like to be able to create epics where tickets within the epic are able to be moved to another board without losing their link to the parent epic. For example, if i have a "Blue Project" and a "Red Project", and I create an epic "Epic A" under Blue, I want to be able to move a child ticket into Red while maintaining it as part of Epic A. Is this possible?
Do I need to do something special to turn this ability on? Today when I move tickets to another board, they lose their association with the parent epic and I am unable to reassign it, as the list of epics given is only whatever is on that board.
Hi @Lea Geyser , do you want to actually "link" the issue to the Epic or do you want to have the issue as a child of the Epic. Regardless you certainly can do either. There are no restrictions that an issue can only be associated with an epic in the same project.
I want to have the issue as a child. Right now, when I click on "add an epic" to a ticket on a certain board, I only see epics that are on that same board - it does not give me the option to select an epic from another board.
I think this is where the issue lies: On the portfolio level we have our team, Demand Gen. On the project level we have the ticket type, e.g. banners, video etc. Then on the task level we have each creative brief request. I think the problem lies in our structure.
We should make the portfolio our ticket type and within that we will have each creative brief request which will be a project. With that structure we can create tasks in the project instead of our current method which is creating sub-tasks in our task. WHEW. Confusing until I break it down in my head like this:
Any update on this? I am also seeing this issue - we are a new Asana customer but have many existing Jira projects and it will be laborious to manually change all of the jira tickets in order for them to appear in Asana.
There are some third-party plugins for this sort of functionality, but if you don't want to do that and your admin won't set up a notification schema, you have only three other choices that I'm currently aware of.
The notification schema is often problematic because most organizations use JIRA for individual assignment rather than assigning to teams with a distribution list address, so it can become quite noisy. Whether or not the schema can be fine-tuned for just your projects so that the only person annoyed is you is something you may need to discuss with your administrator. As I consider the default JIRA approach to individual tickets an inherent anti-pattern, I've never explored using that particular option the way you describe, so I can't advise you on how to do it that way.
Include the Custom Event in Notification Scheme.But You will still need JIRA Administrator permission to configure the Notification Scheme so better to go with the 3rd option stated by Todd"Periodically check your project and add yourself as a watcher to all issues."
Projects in hubspot is nice because in theory it could be used to manage crm development without cluttering the portal with tickets and notes. issue is that they are not really ticket based and don't allow for a reporting interface on it.
Would be awesome if it borrowed some functionality from ticketing and also included a form for ticket creation reps could go to to make requests that both our Admin could see and hubspot product could peek at to see what people are asking for. It's hard to get them to come here to the community when they want a feature.
You can also call for a reservation at (209-549-9341) you will receive a confirmation call, You can also email your request at In...@prospecttheaterproject.org and indicate which performance you would like to attend, the number of people in your party, and provide a phone number, we will email your confirmation.
Build events, create tickets & publish them for your audience. You can do the following: Create events from the app, keep in draft mode and make them live once tickets are added. Tickets can be charged or offered free of charge with service fees...
The main work space displays a standard ticket table. Refer to Searching and managing tickets. Two additional tool buttons allow you to create a new ticket that will be associated with the project, or associate an existing ticket to the project.
This year fundraising for The Glass Float Project will take place right here, on our website! Buy a ticket or two or three between now and Sunday, October 20, at 4 p.m. and your name will be entered into our drawing that many times. Buy 2 tickets and your name will be in the hopper 2 times; buy 4 tickets and your name will be in there 4 times, etc. SPECIAL: BUY 10 TICKETS AND GET TWO MORE FREE! Add 12 to your cart and pay only $100. We will choose names by random number generator Sunday evening, Oct. 20 at 7 p.m. EST, on Facebook Live. You do not have to be watching to win--we will contact you if you won. Prizes will include a Block of Block, colored floats, clear floats, BI stemless wine glasses, gift certificates, and other great prizes tba! Thank you for your support, and we will see you out on the island! Happy hunting!
The Des Moines Storytellers Project strongly believes that everyone HAS a story and everyone CAN tell it. None of the storytellers who take our stage are professionals. They are your neighbors, friends or co-workers, and they are coached to tell by Register journalists.
The Des Moines Storytellers Project is a series of storytelling events in which community members work with Register journalists to tell true, first-person stories live on stage.The project is dedicated to the idea that oral storytelling and journalism have the same goals: Serving and reflecting a community while fostering empathy.
A Special Thank You to the riders who cruised aboard the Battleship when she returned to her Pier at the Camden Waterfront on June 20. Your donations are most appreciated and will help the ship as she prepares to re-open for guest to come back aboard.
A Thanks to the guests who cruised about the Spirit of Philadelphia as she met the Battleship at the Walt Whitman Bridge and traveled back with her to the Camden Waterfront. The donation for the cruise will help cover the costs of the dry dock project for the Battleship, a non-profit museum and memorial. Thank you!
Thank you to everyone who supported the Battleship and donated for Dry Dock Guided Tours of the ship while she was in the Philadelphia Navy Yard. Your donation for the tour helped to offset the loss of revenue by having the Battleship closed this spring for onboard tours, group tours, special events and overnights.
A special thank you to the participants in the Battleship Dry Dock Departure Celebration goes to speakers during the celebration, which included NJ Gov. Phil Murphy, Con. Don Norcross, RADM Thomas Anderson USN, NJ Assembly Speaker Craig Coughlin, Camden County Commissioner Director Louis Cappelli Jr., Camden Mayor Victor Carstarphen, Master Chief Keith Cameron USN of the Submarine New Jersey (SSN-796), LCDR Chaplain James Johnson USN, and Battleship CEO Marshall Spevak.
USS New Jersey was dry docked for major work on at least three separate occasions in her last decade of service, which is the norm for an active vessel. Her most recent dry-docking was from late 1990 into 1991 when she was being deactivated and prepared for the mothball fleet. For an active vessel dry-docking every couple of years is common and necessary, for a museum ship 20-year intervals is acceptable and common. It will be over 30 years before the ship is finally dry-docked.
The ship will be towed to the drydock where the ship will be taken out of the water. The priority for this project is to remove the marine growth on the hull, repaint the hull, inspect the through-hull openings and other sensitive areas, and replace the anodes used for cathodic protection.
Fifteen guests can ride aboard the Battleship when she departs the Philadelphia Navy Yard and is towed to the Paulsboro Marine Terminal on June 14. Fifteen guests can also ride aboard the Battleship when she departs the Paulsboro Marine Terminal and returns to the Camden Waterfront on June 20. Tickets to ride aboard the Battleship are a $5,000 donation per person for each trip.
Work will begin when the Battleship arrives at Dock #3 at the Philadelphia Naval Ship Yard. The Battleship left her current berth at the Camden Waterfront on March 21. She will be worked on for roughly 12 weeks. Her return to the Camden Waterfront is scheduled for June 20.
93ddb68554