How to make records stay in synch across 2 tabs

This isn’t really how Airtable works with regard to record linking. You can hack something together using automations (when status=X in table 1, create record in table 3), but the better method is using linked record fields to either associate the records in table 1 and table 2 as necessary, or use linked record fields to associate records from table 1 and table 2 to a record in table 3 (this is a junction table). Then you can use lookup fields to display updated record info from one table in the other table, so you’re not entering data twice. 

With a bit more info about what you’re trying to accomplish (collating two contact lists, or whatever) we can provide a bit more honed advice.

What am I trying to do?

Tabs 1 and 2 are issues raised that become tasks. In tab 3, I want to show the complete set of records or tasks still OPEN from Tab1 and Tab 2 combined. Tab 3 gives a third party a single Tab to see all open tasks.

The Problem:

I created tab 3 manually and I am now updating the comments made in Tab 1 into Tab 3. Then data from field updates from Tab 3 into Tab 1. Very ungraceful, somewhat disgraceful. 

The Solution?

I could just eliminate the combined tab 3 and have the third party look at Tab 1 and Tab 2 separately.

Any particular reason why Table 1 and Table 2 aren’t combined? If they’re the same type of data (issue tickets or whatnot) the cleanest methodology is to consolidate into one table.

If that’s not an option (two different companies or something), then my mind goes to two automations that create a basic record in table 3, with a linked record to table 1 or table 2. Then add various lookup fields. Finally consolidate the lookup fields with formula fields that have very basic IF logic so if the lookups are drawn from table 1, they’re shown, otherwise the lookup from table 2 is shown. 

Another quick tip is to not use the official Airtable comments function for this, those comments are pretty inextricably tied to the original records and can’t be accessed via automation or lookup. Make sure any comments on your issues are put in long text fields associated with the records. 

I had used autonumber field type to generate the issue number. When I paste Tab 2 records into Tab1, the Issue numbers gets corrupted as the autonumber keep scaling up the Issue numbers for the pasted records. 

Okay so why are you pasting from table 2 to table 1? Are they populated differently (user forms vs manual entry, etc)? Are table 2 records like sub-tasks or something related to table 1? 

Autonumber is a bit of a bear, because it autonumbers everything. That said for end users they don’t really care if their ticket request # is sequential to Johnny’s from 3 offices down. You can also devise a formula to act as a ticket number without autonumber (something like Requester’s Name & Submission Date, etc.)

If they really are the same type of ticket data, I’d manually reconcile once and consolidate all entries into table 1